Skip to main content

MCP connector

For Studio users with the URL of a Model Context Protocol (MCP) server that speaks streamable HTTP, and any credentials it needs. Studio discovers the server's tools and drafts the guide from them; in chat the agent connects to the server itself and calls the tool the guide names.

Before you start: the URL must be the public http or https endpoint that answers; Studio supports streamable HTTP only and does not follow redirects.

Steps​

  1. Open Data Connectors, click Create Connector, choose MCP Server and fill Connector Name, Description and a one-sentence Connector Guide (step 5 expands it).
  2. In Connection Configuration ("The MCP server endpoint (streamable HTTP). Agents connect to it directly from their sandbox using the credentials stored in Secrets Manager."), enter the MCP Server URL, for example https://mcp.example.com/mcp.
  3. In Authentication Configuration, add credentials only if the server needs them: choose Credential placement (HTTP headers or URL query parameters), then fill rows of Credential key, an optional header name and Value, up to 12 with Add credential. The guidance ends "Leave empty for unauthenticated servers."
  1. Click Test Connection. Studio opens a streamable HTTP session with the form's credentials and completes the protocol's initialize handshake; a tick means the server answered, a cross shows the connection error.
  2. Click Discover Tools & Enrich Guide. Studio lists the tools (name, description and argument schema) and streams a guide naming each tool and when to use it. Edit it, then click Accept & Use This Guide (or Discard). The result line reads "Tool discovery and guide enrichment completed successfully!".
  1. Click Create Connector (v1), enabled when name, description, guide and URL are set and, once a test has passed, a discovered guide is accepted.
  2. Open the agent, choose Configure, and add the connector (Agents: configure and activate).

What you should see​

The list shows MCP Server "(v1)", Active. Configuration shows the server URL, the transport (streamable_http) and the authentication type (none without credentials); credentials, if any, appear masked with a View toggle.

In chat​

The agent's code connects to the URL with the stored credentials (headers attached; query-parameter credentials already part of the URL it receives), lists the tools and calls the one the guide names for your request. The prebuilt execution environment image includes the fastmcp client; a custom image needs it too (Execution environments).

Recipe: this documentation as a connector​

This site publishes a read-only MCP server at https://docs.alphaagent.prometheusrl.com/mcp. It needs no credentials and offers three tools: search, fetch and list_sections.

  1. Create Connector, type MCP Server; name it "Product documentation" and write a guide such as "Answers questions about AlphaAgent Studio and Organisations from the public documentation."
  2. MCP Server URL: https://docs.alphaagent.prometheusrl.com/mcp; leave Authentication Configuration empty.
  3. Test Connection, then Discover Tools & Enrich Guide; the proposed guide lists the three tools. Accept & Use This Guide.
  4. Create Connector (v1), add it to an agent, and ask "How do I create a Snowflake connector?": it calls search, then fetch, and answers from the page. To use the server from other tools, see Connect your agent.

Notes​

  • Limits: streamable HTTP only; public hosts (no private, loopback, link-local or metadata addresses), redirects not followed; session timeout 30 seconds by default; 12 credential rows; one placement per connector.
  • Test Connection fails: check the URL is the endpoint itself (not a page that redirects to it), reachable from the internet, with credentials in the placement the server expects. An address error on save: the URL resolves to a private or reserved address.
  • Discovery finds nothing useful: the server advertised no tools, or thin descriptions; edit the guide before accepting. Create Connector (v1) disabled after a passing test: run discovery and accept a guide.
  • A tool call fails in chat: the server-side credentials may have rotated; open Update, re-enter the values under Credentials and save a new version.