Configure Claude to use the Staffbase MCP Server with OAuth, so it can securely access Staffbase content and run Staffbase MCP Server tools on behalf of the signed-in user.
This guide describes one possible setup based on Staffbase testing. Steps can vary depending on your Claude configuration, environment, and access permissions. Staffbase maintains the Staffbase platform and MCP Server, while Anthropic maintains Claude and related components. For the latest Claude-specific instructions, refer to Anthropic’s Managed MCP documentation.
Prerequisites
- You are an administrator in your Staffbase platform.
- You have OAuth clients activated for your platform. Contact Staffbase Support or your Customer Success Manager for more information.
- You have permissions and knowledge to configure MCP server connections in Claude.
Step 1: Identify the MCP endpoint
You need to identify your MCP Server endpoint. The MCP Server is served from the same domain as your Staffbase platform.
If your platform domain URL is https://mycompany.com, your MCP server endpoint is https://mycompany.com/mcp
Step 2: Collect the redirect URIs and origins of Claude
Claude completes the authorization code flow on fixed callback URLs depending on where it runs. Use the callback URL and browser origin that match your Claude setup. Browser-based Claude uses a hosted callback URL and an origin such as https://claude.ai. Local Claude clients use a loopback callback URL and do not require a browser origin.
Callback URL examples for Claude clients:
| Claude client | Environment | Callback URL |
|---|---|---|
| Claude web | Browser | https://claude.ai/api/mcp/auth_callback |
| Claude Code, Claude Desktop | Local machine | http://127.0.0.1/callback |
Step 3: Create an OAuth client for Claude
Create an OAuth Client with the following configuration:
| Setting | Value |
|---|---|
| OAuth Client Type | SPA |
| Client name | MCP Note: The Client Name must be exactly MCP. The MCP Server resolves its OAuth configuration by this name, and authorization fails if the name differs. |
| Redirect URIs | Use the Claude callback URL(s) from Step 2 for each environment you support, for example web, desktop, or CLI. |
| Scopes | Enter a single whitespace character. The MCP Server does not require specific OAuth scopes. |
| Allowed CORS origins | Add Claude browser origin(s) that call the MCP endpoint, for example https://claude.ai. Loopback or local clients do not require CORS origins. |
Step 4: Register the MCP Server endpoint in Claude
Add your Staffbase MCP endpoint in Claude and register the connection. Access the available tools.
Step 5: Authorize the Claude connection
- Start the connection from Claude.
- In the browser window that opens, sign in with your Staffbase account. Claude acts with the permissions of the account you sign in with.
- After you sign in, Claude reports a successful connection.