Connect InvesTeam to Other AI Clients

To connect InvesTeam to any MCP client, point the client at the server's URL over streamable-HTTP and send your hfk_ key as a Bearer token. The InvesTeam server is a standard streamable-HTTP MCP server, so any conformant client — not only Claude — can discover and call its tools the same way. Output is decision-support analysis, not investment advice.

How do I connect InvesTeam to any MCP client?¶

Give your client three things: the transport (streamable-HTTP), the server URL, and your hfk_ key as an Authorization: Bearer header. The server forwards that key verbatim to the public API on every tool call and holds no credential of its own.

A generic streamable-HTTP MCP client config looks like this. It is a single-language JSON block — not affected by the code-language toggle.

{
  "mcpServers": {
    "investeam": {
      "type": "http",
      "url": "https://mcp.investeam.io",
      "headers": { "Authorization": "Bearer hfk_your_key_here" }
    }
  }
}

Replace hfk_your_key_here with your key. Once connected, list the tools and run the agent loop. If your client uses a different key for its config field names, keep the header exactly as Authorization: Bearer hfk_… — that is what the server reads.

What scopes does my key need?¶

Match the scope to what your agent does: pipeline:write to submit (create_brief, answer_clarifications), pipeline:read to poll and read (get_brief, list_sessions, get_orchestration), and pipeline:findings to read the final analysis (get_analysis). See Authentication & API Keys for issuing and scoping keys. If a submit tool returns forbidden, the key is missing pipeline:write.

Does the server support stdio as well as HTTP?¶

Streamable-HTTP is the default and the recommended transport for a hosted connection. The server can also run over stdio for a locally launched process; the key-forwarding contract is identical either way — the tool still reads your hfk_ key from the request and forwards it verbatim. Most hosted clients use the HTTP URL above; use stdio only when your client launches the server itself.

What are the most common connection failures?¶

Two mistakes cause nearly every first-run failure: a wrong endpoint URL and a missing or under-scoped key. If tool calls return unauthorized, check the Authorization header is present and well-formed. If a submit tool returns forbidden, your key is missing pipeline:write. A missing key fails closed — the tool returns unauthorized and makes no upstream call.

What's next?¶

See the MCP Tool Catalog for every tool and its backing endpoint, and Agent Patterns for the submit→poll loop, cadence, and terminal states. For the Claude-specific setup, see Connect to Claude.