MCP integrations
Connect a supported remote MCP server, authorize access and inspect its tools.
What the connection does
A remote MCP server exposes tools that a Chippi agent can use when the connection is configured and made available to it. This setup brings tools into Chippi; it is not a public API for reading your Chippi workspace from another application.
Prepare the server information
Use the server address and authentication instructions supplied by the tool provider. Remote endpoints should use HTTPS. Do not put credentials in the server URL or paste secrets into a task prompt.
The endpoint must implement a transport supported by the MCP setup. The HTTP connection uses the server endpoint rather than a normal website address.
Add the server
Open the MCP server setup in the AI workforce tools area. Add the server name and address, choose the supported transport, and supply the required authentication through the connection settings.
Complete the authorization flow when the server requests OAuth. A cancelled or unfinished authorization is not a working connection.
Inspect the tools
Refresh the server’s discovered tools and check that the tools you need are present. An endpoint can be reachable without exposing the expected capabilities. If discovery fails, check the address, authentication and provider availability before retrying.
Give the agent the relevant access
Make the connection available to the agent that needs it. Workspace scope, available tools and configured action confirmations still apply. Instructions describe the work; they do not grant account access.
Start with a small task and inspect the result before expanding the work. The outcome depends on the provider, credentials and runtime available for that task.
Keep the setup current
Reauthorize or remove the connection when its account or purpose changes. Refresh discovery when the provider changes its tools. Check the actual connection status instead of treating a saved configuration as proof of a successful action.
Public code examples
Explore the connection, discovery and tool-call examples. They use the official MCP TypeScript SDK v1 and your provider’s endpoint. The examples do not expose Chippi workspace data or private application APIs.