MCP integration

Connect your agent

Streakline exposes a remote MCP endpoint at /mcp on the API host. Configure a Streamable HTTP connection in your MCP client. For clients that accept this configuration shape:

{
  "mcpServers": {
    "streakline": {
      "type": "http",
      "url": "https://api.qa.streakline.dev/mcp"
    }
  }
}

Your MCP client uses browser-based OAuth consent with authorization code and PKCE. Ask your workspace owner to provision a supported public OAuth client and redirect URI for your agent. Dynamic client registration is disabled; public clients do not receive a client secret.

MCP access uses a signed-in workspace member’s permissions and consented scopes. It does not use the server M2M token or the user-bound runtime credential described in the SDK guides.

Available workflows

The curated MCP tools cover:

• Listing accessible projects and reading an environment’s active configuration.
• Listing configuration releases and rendering a configuration flow.
• Creating, reading, saving, and validating configuration drafts when permitted.
• Releasing a draft and deploying a released version to an environment.

Tool availability and success depend on granted OAuth scopes and your current workspace and project role. Releasing and deploying are separate steps. Inspect the draft and target environment before requesting those changes.

Start with a read-only request

Ask your agent to list accessible projects, then inspect the active configuration for a specific environment. Use that result to understand the event keys and rules before drafting changes.

The runtime REST API remains the integration surface for events and user profiles. MCP is the configuration workflow for an authorized workspace member.