MCP

Probara exposes a Model Context Protocol (MCP) server at:

https://probara.net/mcp

Any MCP-compatible client (an AI assistant or IDE) can connect to this endpoint to call Probara’s test-management tools — projects, suites, test cases, runs, defects, and more. See the MCP tool reference for the full, generated list of every available tool.

Authentication

/mcp accepts either credential type as a Bearer token — see API authentication for the full comparison:

• OAuth 2.1 (recommended for interactive clients like Claude.ai, Claude Code, Cursor, ChatGPT) — the client discovers the server, registers itself, and a human approves access via a consent screen. No secret to copy/paste.
• API token (recommended for scripts and headless integrations) — a long-lived probara_... token created in Workspace → API tokens, pasted directly into the client’s Bearer/Authorization field.

Every /mcp request without a valid credential returns 401 with a WWW-Authenticate: Bearer resource_metadata="https://probara.net/.well-known/oauth-protected-resource" header pointing the client at discovery.

Claude.ai (custom connector)

1. Open Settings → Connectors → Add custom connector.
2. Enter the server URL: https://probara.net/mcp.
3. Claude.ai discovers the OAuth metadata automatically, registers itself (Dynamic Client Registration), and redirects you to Probara’s consent screen.
4. Pick the organization to bind the connection to and approve. Claude.ai now has an OAuth grant scoped to that organization.

Claude Code

1. Add the server: claude mcp add --transport http probara https://probara.net/mcp.
2. Claude Code opens a browser window for the OAuth authorize/consent flow (same discovery + DCR as Claude.ai).
3. Approve the negotiated scopes and pick an organization. If the client omits scope or sends a value Probara doesn’t recognize, it defaults to the full supported set (mcp:read mcp:write); see Scopes for the exact negotiation rules.
4. Verify the connection: claude mcp list should show probara as connected.

Cursor

1. Open Settings → MCP → Add new MCP server.
2. Choose HTTP transport and set the URL to https://probara.net/mcp.
3. Cursor follows the same OAuth discovery/DCR/consent flow; alternatively, paste an API token into the connector’s Bearer/Authorization header field if your Cursor version does not yet support MCP OAuth.

ChatGPT

1. Open Settings → Connectors → Add MCP server (Developer Mode / custom connectors).
2. Set the server URL to https://probara.net/mcp.
3. Complete the OAuth consent flow, or supply an API token as a Bearer header if your ChatGPT plan only supports static-header connectors.

Troubleshooting

Symptom	Likely cause
401 immediately, no browser prompt	Client does not support MCP OAuth discovery — use an API token instead
Consent screen shows the wrong organization	Pick a different organization on the consent screen’s org picker before approving; each grant binds to exactly one organization
A tool call returns forbidden	The OAuth grant only has mcp:read, or your role in that organization no longer permits writes — see Authentication
429 too_many_requests	Per-token or per-organization rate limit hit — back off and retry