Skip to content
Last updated

Connect to the Integrations Hub MCP

Use the hosted Integrations Hub MCP server from an AI client to inspect your developer account, configure an application, and test it on a Location you control. The server provides tools for the owner-side application lifecycle; Marketplace administrators handle moderation and publication.

What you'll have at the end

  • An MCP client connected to your Altegio developer account.
  • Access to application, installation, and status tools from that client.
  • A read-only first request that confirms the connection works.

Before you start

You needWhy
An Altegio account with access to your developer applicationsThe server uses your account's permissions. You can only manage applications and Locations available to that account.
An MCP client that supports remote Streamable HTTP serversExamples below cover Claude Code and Cursor. See the client connection guide for other clients.

No local server installation or API token is required for the hosted connection.

Step 1 — Add the MCP server

Use this MCP endpoint in your client:

https://mcp.alteg.io/integrations-hub

The URL above is the server address itself. The longer https://mcp.alteg.io/integrations-hub/mcp path also works for existing client configurations.

Claude Code

Run:

claude mcp add --transport http altegio-integrations-hub https://mcp.alteg.io/integrations-hub

Then run /mcp in Claude Code and choose Authenticate.

Cursor

Add this entry to ~/.cursor/mcp.json or your project's .cursor/mcp.json, then reload Cursor:

{
  "mcpServers": {
    "altegio-integrations-hub": {
      "url": "https://mcp.alteg.io/integrations-hub"
    }
  }
}

Other clients

For Claude, VS Code, Codex, Gemini CLI, ChatGPT, and other supported clients, follow the client-specific connection instructions. In a client that accepts a custom remote MCP server URL, enter the endpoint above and complete the sign-in flow. Your workspace settings may restrict who can add connectors.

Step 2 — Authenticate

When your client prompts you to connect, sign in with the Altegio account that has access to your developer applications. Complete the authorization flow in your browser, then return to the client.

Step 3 — Verify the connection

Start with a read-only request:

List the developer accounts I can access and the applications in each account. Do not change anything.

You should see only the accounts and applications your Altegio user can access. If the client does not show the server's tools, check that the MCP server is enabled in the client and that authentication completed.

Available tools

AreaWhat you can do
Developer account and applicationInspect accounts, catalog metadata, and available rights; create a private draft; update its card, assets, settings, and callbacks.
Installation and testingConnect an application to a test Location, activate an installation when required, and inspect installation status.
Embedded experiencesConfigure entity frames and sidebar integrations, including supported chat and highlight controls.
Billing and notificationsInspect tariffs and payment links, manage supported payment actions, and configure notification channels and SMS sender names.
PerformanceRead application statistics, conversion statistics, and reviews.
Rollout guidanceRead the built-in draft rollout guide and implementation resources.

Plan changes before applying them

Write tools support mode=plan to show proposed changes before mode=apply performs them. Ask your client to inspect the available rights and return a plan before it creates or changes an application. Review the plan, then approve the specific action you want to apply. Sensitive actions require an exact confirmation phrase.

For example:

Read the Integrations Hub rollout guide and available rights. Plan a private application draft for my test Location with the minimum permissions needed. Show the proposed changes and wait for my approval before applying anything.

The MCP can prepare an application and submit it for moderation. Marketplace administrators make the moderation and publication decisions.

If something goes wrong

SymptomWhat to check
The client cannot connectConfirm the URL is https://mcp.alteg.io/integrations-hub and that your client supports remote Streamable HTTP MCP servers.
Authentication does not completeReturn to the client after signing in and retry its connection or authentication action.
An account or application is missingSign in with an Altegio user that has access to that developer account or application.
A write action is unavailableCheck the account's available rights and the action's required confirmation. Start with mode=plan.