read thedocs.

[ docs // guides & reference ]

Connector setup guides, tool references, auth flows, and platform concepts — everything you need to run StackJack, in one place.

Browse the Docs All Connectors
34 connectors documented // 6,712 tools referenced // setup, auth & platform guides
↓

No pages match that search. Clear it

← All documentation

Connect other MCP clients (Microsoft Foundry and generic)

StackJack works with any MCP client that supports Streamable HTTP transport (MCP is the Model Context Protocol, the open standard AI tools use to call external tools). This page covers Microsoft Foundry, which needs a credentialed connection, plus the reference values for wiring up any other client.

Microsoft Foundry

Foundry uses a credentialed project connection — there is no URL-only sign-in — so have an owner, co-owner, or Administrator create an MCP client or API key first (see Managing MCP credentials).

  1. Open your project and agent. In ai.azure.com, open (or create) a project and an agent.
  2. Add a custom MCP tool. Go to Add Tools → Custom tab → Model Context Protocol → Create. Set the name (server label) and the server URL https://mcp.stackjack.io/mcp.
  3. Add the credential. Create a project connection with a credential name and value — either:
    • name Authorization, value Basic <base64(CLIENT_ID:CLIENT_SECRET)>, or
    • name X-API-Key, value sjk_...
  4. Set approvals and scope. Set require_approval to never for unattended runs, and optionally list allowed_tools to scope which tools the agent can call.

Generic MCP client reference

For any other MCP client, these are the values you need:

Setting Value
Endpoint https://mcp.stackjack.io/mcp
Transport Streamable HTTP
Sign-in If the client supports OAuth, add the URL alone and complete the browser sign-in (the client registers itself automatically) — no header needed
Auth header (manual client) Authorization: Basic <base64(CLIENT_ID:CLIENT_SECRET)>
Single header (API key) X-API-Key: sjk_... (or Authorization: Bearer sjk_...)

Notes:

  • Prefer the sign-in path wherever the client supports it — no secrets to store, and access follows your team membership. See How AI tools authenticate.
  • A credential only works in its own lane: an API key cannot be sent as Basic auth, and a Client ID + Secret cannot be sent as an API key.
  • If the client rejects the connection with a 401 that mentions OAuth metadata, that's normal discovery behavior — it means the client found StackJack but hasn't authenticated yet.

Tool limits

Whatever the client, keep the tool list purposeful: StackJack can expose hundreds of tools depending on your connectors and plan. Use a client credential with a restricted tool selection (and the harness's own tool filtering, like Foundry's allowed_tools), or switch StackJack to compact catalog mode so it serves a small tool list and the client discovers the rest on demand. An admin must first enable catalog modes for your organization on Endpoints; until then StackJack serves the full tool list. See Choosing tools for each client and managing harness tool limits.

Troubleshooting

See Connection troubleshooting for the common failure signatures across all clients.