Skip to content

MCP Server

The Jetstack MCP server lets an AI assistant use your Jetstack AI account through the Model Context Protocol. Your assistant can then do the same things the REST API does.

Server URLhttps://mcp.jetstack.ai
Also answers athttps://mcp.jetstack.ai/mcp, for clients that expect a path
TransportStreamable HTTP (remote server)
Sign-inOAuth, using a Jetstack access token

Every tool calls the Jetstack REST API with your access token. An assistant can only do what that token’s scopes allow.

You need a Jetstack access token.

  1. In the Jetstack app, go to Settings → Access Tokens.
  2. Create a token. Pick the scopes the assistant needs. See Scopes below.
  3. Copy the token. It starts with jsai_ and is shown only once.

For more on tokens and scopes, see Authentication.

Any MCP client that supports remote HTTP servers with OAuth can connect. Add the server URL, and the client opens the Jetstack sign-in page.

Add Jetstack as a custom connector in Claude (web or desktop).

  1. Open Settings → Connectors.
  2. Choose Add custom connector.
  3. Name it Jetstack AI and enter https://mcp.jetstack.ai as the URL.
  4. Select Connect. Claude opens the Jetstack sign-in page. Complete Sign In.

Custom connectors are available on Claude plans that support them. On Team and Enterprise plans, an owner may need to add the connector for the organisation first.

The Jetstack sign-in page asks for two values.

FieldWhat to enter
Instance IDEnter default. If your organisation runs on a dedicated Jetstack instance, paste the Instance ID shown in Settings → Access Tokens → Connection Details instead.
Access TokenYour jsai_… token.

Select Connect. Jetstack checks the token, then sends you back to your client. The tools are ready to use.

  • Your token is never shown to the AI assistant. The client holds a session that Jetstack issues, not your token.
  • Revoking the token ends access. Tool calls fail as soon as the token is revoked in Jetstack, and the session closes at its next hourly renewal.
  • A session lasts 30 days. After that, your client asks you to sign in again.

Each tool needs a scope on your token. If the token is missing it, the tool returns an error that names the scope it needs.

  • Read-only covers listing portals, library assets, modules, tasks, audits and Projects. It doesn’t include browsing HubSpot.
  • Operator adds browsing, importing and deploying HubSpot assets, and creating and running audits.
  • Projects write scopes (projects:write, projects:chat, projects:generate, projects:admin) are added one by one.
  • projects:deploy and projects:billing are never part of a preset. Add them on purpose, only to tokens that should deploy Projects work to HubSpot or buy credits.
  • “List my connected portals, then show the workflows in the Acme production portal.”
  • “Find the best MQL workflow across all my portals and draw it as a diagram.”
  • “Import the lead-routing workflows from the sandbox, then deploy them to production. Show me the mapping before you deploy.”
  • “Run the standard audit on the Acme portal and summarise the five biggest problems.”

The server has 24 core tools and 72 Projects tools. Your client lists them all, with their inputs, once you connect.

Most tools take IDs that other tools return. A typical order is list_portals → browse_hubspot → start_import → get_task, or list_assets → get_mapping_structure → get_mapping_destinations → start_deploy.

ToolWhat it doesScope
list_portalsLists the HubSpot portals connected to your organisation, with the portal IDs other tools need.portals:read
browse_hubspotLists assets in a connected portal: workflows, forms, emails, lists, pipelines, pages, templates, blog posts, HubDB tables, properties, property groups or custom objects. Returns the HubSpot IDs used for import.hubspot:browse
preview_workflow_mermaidFetches a workflow live from HubSpot and returns it as a Mermaid flowchart, without importing it.hubspot:browse
scan_portal_profilesProfiles a portal’s workflows, lists, forms, emails or pipelines, so the assistant can match them to a use case. Cached for 24 hours; pass fresh to re-read HubSpot.hubspot:browse
scan_all_portals_profilesProfiles one asset type across every connected portal, for questions like “which of my portals has the best MQL workflow”. Cached for 24 hours per portal.hubspot:browse
ToolWhat it doesScope
start_importImports selected HubSpot assets into your Jetstack library, and can create a module from them. Returns a task ID.hubspot:import
list_assetsLists assets in your library, filtered by type or source portal. Returns the library IDs used for mapping and deploy.assets:read
search_library_profilesSearches structured profiles of imported assets: properties used, dependencies, enrolment criteria and actions.assets:read
get_asset_detailReturns the full stored data for an imported asset, including its HubSpot definition and dependencies.assets:read
get_workflow_mermaidReturns an imported workflow as a Mermaid flowchart, labelled with email names, list names, property values and delays.assets:read
list_modulesLists your modules: collections of assets that deploy together.modules:read
get_moduleReturns one module with its asset breakdown.modules:read
ToolWhat it doesScope
get_mapping_structureShows what has to be mapped before a deploy from one portal to another: properties, owners, pipelines and more, marked required or optional.hubspot:deploy
get_mapping_destinationsLists the matching options in the target portal for one mapping type, such as properties, owners, pipelines, lifecycle stages, teams or association labels.hubspot:deploy
start_deployDeploys library assets or modules to a target portal with the mapping you provide. Returns a task ID.hubspot:deploy
ToolWhat it doesScope
list_tasksLists import and deploy tasks. Filter by type, or by status: pending, processing, completed, incomplete or failed.tasks:read
get_taskReturns a task’s progress for each asset, so you can see what succeeded and what failed.tasks:read

A task that ends as incomplete has finished, but some assets were skipped or have unresolved dependencies. Filtering by completed doesn’t include it.

ToolWhat it doesScope
list_audit_blocksLists the blocks you can put in an audit template. Filter by report type or category (general, sales_hub, marketing_hub, service_hub, automation, reporting).audit:read
list_audit_templatesLists Jetstack’s built-in templates and your organisation’s own.audit:read
get_audit_templateReturns a template’s blocks and tier requirements.audit:read
create_audit_templateCreates a custom template from block IDs. Use report type SIMPLE for audits run through the API.audit:write
run_auditStarts an audit on a portal using a template, in quick or full mode. Returns an audit run ID. Only SIMPLE templates run here; ADVANCED templates need the Chrome extension.audit:write
get_audit_statusReturns an audit run’s status: created, processing, completed or failed.audit:read
get_audit_dataReturns the full report for a completed run: blocks, data points, recommendations and health scores.audit:read

Projects tools work on Projects. They need Projects to be turned on for your organisation. Check with get_projects_enabled, or see Getting Access.

What a token can do on a project is the overlap of two things: the token’s scopes, and the project role of the person who created the token. A token can never do more than its creator. Call get_project_access to see which actions are available before you write.

Write tools that start long work take an idempotencyKey. Reuse the same key when you retry the same call, and use a new key for new work.

ToolWhat it doesScope
get_projects_enabledChecks whether Projects is turned on for your organisation.projects:read
list_projectsLists projects, with search, status filter and paging.projects:read
get_projectReturns a project’s settings, portal and status.projects:read
get_project_overviewReturns everything the project’s Overview page shows, as data.projects:read
get_project_accessReturns your role, capabilities and the actions available to this token on a project.projects:read
get_projects_rolesReturns the table of project roles and what each one can do.projects:read
get_projects_openapi_jsonReturns the OpenAPI document for the Projects API.projects:read
create_projectCreates a project on a HubSpot portal.projects:admin
rename_projectRenames a project.projects:admin
delete_projects_by_projectIdArchives a project. Deployed objects stay in HubSpot and the history is kept. Archived projects can’t be restored.projects:admin
ToolWhat it doesScope
get_project_creditsReturns your organisation’s Projects credit balance.projects:read
get_projects_credits_historyLists credit ledger entries, newest first.projects:read
post_projects_credits_purchasesStarts a credit purchase and returns a checkout link. A person completes the payment in a browser. Needs an organisation admin.projects:billing
get_projects_credits_purchases_by_sessionIdReturns the status of a credit purchase.projects:read
ToolWhat it doesScope
get_projects_members_by_projectIdLists a project’s members and their roles.projects:read
get_projects_members_candidates_by_projectIdLists organisation members who could be added.projects:admin
post_projects_members_by_projectIdAdds a member to a project.projects:admin
patch_projects_members_by_projectId_userIdChanges a member’s role.projects:admin
delete_projects_members_by_projectId_userIdRemoves a member.projects:admin
ToolWhat it doesScope
get_projects_portal_by_projectIdReturns what Jetstack knows about the project’s portal.projects:read
put_projects_portal_by_projectIdBinds the project to its portal. Refused if the project already has one.projects:admin
get_projects_portal_onboarding_by_projectIdReturns the state of the first portal scan, and whether the project is ready to use.projects:read
post_projects_portal_rescan_by_projectIdRe-reads the portal. Returns a refresh ID to poll.projects:write
get_projects_portal_refreshes_current_by_projectIdReturns the portal refresh in progress, or the most recent one.projects:read
get_projects_portal_scan_gate_by_projectIdSays whether a Chrome extension scan can run, and what’s missing if not.projects:read
post_projects_portal_scan_by_projectIdQueues a Chrome extension scan. Someone must then run it from a signed-in HubSpot tab with the extension open.projects:write
get_projects_portal_objects_by_projectIdLists the objects Jetstack has seen in the portal.projects:read
get_projects_portal_objects_by_projectId_domain_hubspotIdReturns one portal object, with a preview, facts and where they came from.projects:read
get_projects_portal_relationships_summary_by_projectIdSummarises how the portal’s objects connect to each other.projects:read
get_projects_portal_relationships_neighborhood_by_projectIdReturns the objects connected to one object.projects:read
ToolWhat it doesScope
post_projects_documents_by_projectIdUploads a document (up to 20 MB, sent as base64) and starts reading it.projects:chat
get_projects_documents_by_projectIdLists uploaded documents.projects:read
get_projects_documents_by_projectId_documentIdReturns one document, with what was extracted from it.projects:read
get_projects_documents_download_by_projectId_documentIdReturns a download link for the original file.projects:read
post_projects_documents_analyze_by_projectIdAnalyses documents into Project Knowledge. Spends credits.projects:generate
get_projects_operations_by_projectIdLists long-running operations, such as document analysis and planning.projects:read
get_projects_operations_by_projectId_operationIdReturns one operation’s progress.projects:read

See Project Knowledge for how the brief and decisions work.

ToolWhat it doesScope
get_project_knowledgeReturns the published project brief: summary and metrics.projects:read
get_projects_knowledge_brief_by_projectIdReturns every item in the brief.projects:read
get_projects_knowledge_claims_by_projectIdReturns the claims behind the brief, with their evidence.projects:read
get_projects_knowledge_versions_by_projectIdLists published Knowledge versions, newest first.projects:read
get_projects_knowledge_versions_by_projectId_versionReturns one Knowledge version in full.projects:read
list_project_decisionsReturns the decisions waiting for an answer, with evidence and the allowed answers.projects:read
get_projects_knowledge_decisions_by_projectId_decisionIdReturns one decision.projects:read
resolve_project_decisionAnswers one decision. Pass the version from list_project_decisions; out-of-date answers are refused.projects:write
post_projects_knowledge_reviews_by_projectIdSubmits several decisions at once.projects:write
get_projects_knowledge_reviews_by_projectIdLists past reviews.projects:read
get_projects_knowledge_reviews_by_projectId_reviewIdReturns one review.projects:read
post_projects_knowledge_suggestions_by_projectIdAsks Jetty to suggest answers to open decisions. Spends credits. Suggestions aren’t applied until someone submits them.projects:generate
get_projects_knowledge_identities_by_projectIdReturns the queue of records that may be the same thing and need a check.projects:read
ToolWhat it doesScope
get_project_blueprintReturns the project’s plan of record and whether a new one can be derived.projects:read
derive_project_blueprintDerives a new Blueprint from published Knowledge. Spends credits.projects:generate
get_projects_blueprint_versions_by_projectIdLists Blueprint versions, newest first.projects:read
get_projects_blueprint_versions_by_projectId_versionReturns one Blueprint version.projects:read
ToolWhat it doesScope
list_project_assetsLists the assets on the project’s canvas. These IDs belong to the project, not your library.projects:read
get_project_assetReturns one asset in full.projects:read
get_project_asset_specReturns an asset’s specification.projects:read
get_projects_assets_description_by_projectId_assetIdDescribes what an asset does, in plain language.projects:read
get_projects_assets_issues_by_projectId_assetIdLists every validation issue on an asset.projects:read
get_projects_assets_impact_by_projectId_assetIdShows what removing or detaching an asset would affect.projects:read
get_projects_assets_hubspot_link_by_projectId_assetIdReturns a link to the asset in HubSpot.projects:read
post_projects_assets_verify_by_projectId_assetIdReads the asset back from HubSpot to confirm it’s live as built.projects:write
post_projects_assets_repair_by_projectId_assetIdRepairs a failed asset. Spends credits.projects:generate
post_projects_assets_restore_by_projectId_assetIdRe-applies the project’s version of an asset, overwriting changes made directly in HubSpot.projects:generate
get_projects_assets_repairs_by_projectId_assetId_idempotencyKeyReturns the record of a repair.projects:read
post_projects_assets_retire_by_projectId_assetIdDiscards a draft, stops tracking an asset (detach), or deletes it from the portal (remove). Remove needs the asset’s exact name as confirmation.projects:deploy
ToolWhat it doesScope
list_project_runsLists build, deploy, verify and scan runs, newest first. queued, running, waiting_on_extension and paused are not finished.projects:read
get_project_runReturns a run’s progress, errors and per-asset results.projects:read
post_projects_runs_resume_by_projectId_runIdResumes a run that paused because credits ran out.projects:generate
get_projects_deploy_log_by_projectIdReturns the project’s deploy receipts. See Deploying & Fixing.projects:read
get_projects_deploy_log_runs_by_projectId_runIdReturns each attempt in one run.projects:read
get_projects_deploy_log_receipts_by_projectId_taskId__ae2b7f7cc0Returns the receipt for one Chrome extension request.projects:read