Connect via MCP

Certyn exposes a remote MCP server over Streamable HTTP so external MCP clients can connect directly to your Certyn workspace.

Server URL

For Certyn Cloud, the MCP endpoint is:

https://api.certyn.io/api/mcp

The public manifest is available at:

https://certyn.io/server.json

Authentication

Certyn MCP uses your existing Certyn user login through Auth0/OIDC.

• Use a normal user sign-in flow when the MCP client prompts for authentication.
• MCP v1 does not support API keys.
• MCP v1 does not support demo tokens.

When an unauthenticated client hits the MCP endpoint, Certyn returns the OAuth protected-resource metadata needed for authorization server discovery.

Pre-registered OAuth clients

Use Certyn's pre-registered public OAuth client when your MCP client lets you provide a client ID. These clients use Authorization Code with PKCE and do not have a client secret.

Requested OAuth scopes:

openid profile email offline_access mcp

Claude

Create a custom connector in Claude with the following values:

MCP server URL: https://api.certyn.io/api/mcp
OAuth Client ID: tpc_nZvCVz9Wdh1yb7VX7VBzi4
OAuth Client Secret: leave empty

The client is registered for both Claude callback domains:

https://claude.ai/api/mcp/auth_callback
https://claude.com/api/mcp/auth_callback

ChatGPT

Use the following client only when ChatGPT shows this exact callback URL in the connector settings:

Callback URL: https://chatgpt.com/connector/oauth/qe61i3KmIVPC
MCP server URL: https://api.certyn.io/api/mcp
OAuth Client ID: tpc_nKin1n5FA7aLTSJjF5N846
OAuth Client Secret: leave empty

ChatGPT callback IDs are workspace-connector specific. If ChatGPT displays a different callback URL, this client ID will not work; that callback must be registered separately.

Cursor

Add Certyn to your user or project mcp.json:

{
  "mcpServers": {
    "certyn": {
      "url": "https://api.certyn.io/api/mcp",
      "auth": {
        "CLIENT_ID": "tpc_jZgoggfpgCQ6q2ZwHeEr2B",
        "scopes": ["openid", "profile", "email", "offline_access", "mcp"]
      }
    }
  }
}

The Cursor client accepts the current desktop, hosted, and legacy callback forms. No CLIENT_SECRET is required.

Providing these client IDs avoids creating a new Auth0 application every time a connector is disconnected and reconnected. Dynamic Client Registration remains available as a fallback for other MCP clients.

Capability model

MCP v1 is tenant-wide and tool-only.

• One MCP connection can access any project or environment your user can already access.
• Project tools accept projectIdOrSlug when context matters.
• MCP prompts and resources are not exposed in v1.
• Certyn MCP exposes direct project-record tools, not a recursive assistant chat tool.

Supported tools

• list_projects
• list_environments
• get_project_wiki
• update_wiki
• list_test_cases
• get_test_case
• list_tickets
• get_ticket
• create_test_case
• create_test_cases_batch
• update_test_case
• list_conversations
• get_conversation

See MCP Tool Catalog for tool arguments and response shapes.

Typical setup flow

1. Add the Certyn MCP server in your client using https://api.certyn.io/api/mcp or https://certyn.io/server.json.
2. If the client supports static OAuth configuration, enter its pre-registered client ID from above and leave the client secret empty.
3. Start the connection and complete the Auth0/OIDC login flow with your Certyn account.
4. Call list_projects and list_environments to discover accessible workspace context.
5. Read current project state with get_project_wiki, list_test_cases, get_test_case, list_tickets, and get_ticket.
6. After explicit confirmation, update project records with update_wiki, create_test_case, create_test_cases_batch, or update_test_case.

Notes

• Authorization and access remain tenant-scoped and permission-scoped exactly like the Certyn dashboard.
• Conversation history tools only return tenant-owned conversations.
• For direct tool details, examples, and response payloads, use the MCP Tool Catalog.