Other clients

The Part3 MCP server speaks the standard Streamable HTTP transport with OAuth 2.1 (RFC 8414 + 9728 metadata, RFC 7591 dynamic client registration, PKCE). Any MCP client that conforms to those specs can connect.

Connection details

You don't need to know any of those endpoints — your MCP client discovers them automatically when it connects to https://mcp.part3.io. They're listed for debugging only.

Generic config shape

Most MCP clients use one of these JSON shapes. Adapt to whatever your client's config format is:

{
  "mcpServers": {
    "part3": {
      "url": "https://mcp.part3.io"
    }
  }
}

or

{
  "mcpServers": {
    "part3": {
      "type": "url",
      "url": "https://mcp.part3.io"
    }
  }
}

or

{
  "mcpServers": {
    "part3": {
      "transport": "http",
      "url": "https://mcp.part3.io"
    }
  }
}

What to expect on first use

1. Your client opens a browser to the Part3 sign-in page (/oauth/login).
2. Sign in with your Part3 email and password.
3. Approve the consent screen (/oauth/consent).
4. Your client receives an opaque access token + refresh token. Both are stored in the client's local credential store; you don't see them.
5. Subsequent requests carry Authorization: Bearer <access_token>. The client refreshes the access token automatically (it has a 24-hour TTL).

Building your own MCP client?

If you're integrating MCP into a custom application, the Anthropic MCP TypeScript SDK and Python SDK both ship with a streamable HTTP client + OAuth helper. Point either at https://mcp.part3.io and the SDK handles discovery, registration, the PKCE flow, and token refresh for you.