Skip to content
certyn logoCertyn
Start Free
RecipesDoc

Connect Your Own MCP Server (Logs, Metrics, an Internal Admin Tool)

Ask Certyn uses your team's MCP server to check logs or set up test data while it tests.

For teams with a remote MCP server who want Certyn to use it in the chat.

Your setup

  • An MCP server on a public HTTPS address, for example for Datadog, Grafana, or an internal admin tool.
  • It signs in with OAuth, a bearer token, or a header such as an API key.
  • You want Certyn to read logs for a failed request, or create test data before it tests.

Say this to Certyn

Connect our admin MCP server at https://admin-mcp.example.com/mcp. Then use it to create a test customer with an expired card, and test the renewal page with it.

What Certyn does

  1. Opens the MCP connect form: the server URL, a name, and a token. With a token, Certyn sends it as Authorization: Bearer <token>. With no token, you sign in with OAuth on the server's page and come back to the chat.
  2. A server that needs only headers that are not secret: Certyn connects it directly (mcp.connection.create, you approve).
  3. Reads the server's tools and shows which ones only read (mcp.tool.list).
  4. Calls a tool when the task needs it (mcp.tool.run), for example to find log lines for a request id, or to create the test customer. Before a tool that can change data, it asks you.
  5. Tests with the result on its Machine, or puts it (like the customer's email) in the goal of a run.

What you get

  • Your logs and metrics checked next to what Certyn sees in the browser.
  • Test data made through your own tool, not by clicking through the UI.
  • Optional: on the Connections page, say when Certyn should use the server, for example "check logs in every release review", and turn single tools off.

Limits

  • Only the chat uses MCP tools, not runs. Let the chat prepare data before a run, or save the tool's API token as a secret variable so a run can call its HTTP API.
  • Certyn connects from its own servers, over HTTPS (streamable HTTP). A server on a private address or behind a VPN cannot be reached, even with a self-hosted runner.
  • A secret header that is not a bearer token (like DD-API-KEY): add it on the Connections page, in Manual headers JSON.
  • A tool call stops after 20 seconds, and long results are cut.
  • A tool counts as read-only only if the server marks it so. Certyn treats every other tool as one that writes.
PreviousA Sentry Error Becomes a Reproduced Bug with EvidenceNextAPI Checks Written in Hurl, Run After Each Deploy