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.

Capability model

MCP v1 is tenant-wide and tool-only.

• One MCP connection can access any project or environment your user can already access.
• Tools accept projectIdOrSlug and environmentKey selectors when context matters.
• MCP prompts and resources are not exposed in v1.
• ask_certyn is non-streaming in v1.

Supported tools

• list_projects
• list_environments
• ask_certyn
• 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. Start the connection and complete the Auth0/OIDC login flow with your Certyn account.
3. Call list_projects and list_environments to discover accessible workspace context.
4. Use ask_certyn with optional projectIdOrSlug, environmentKey, conversationId, and chat context fields.

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.