Talaria
MCP

Give your agent production truth.

Talaria’s hosted MCP server lets your coding agent read errors, traces and replays, link GitHub issues and verify a fix after it ships. One URL. OAuth sign-in. No keys to paste.

Add to CursorOther clients
https://api.newtalaria.com/mcp
Streamable HTTPOAuth 2.1 · PKCE40 toolsRead-only mode
Install

Pick your client.

Same URL everywhere. Your client signs in with OAuth the first time, so there’s no key to paste.

  1. 1
    Add it in one click

    Opens Cursor’s install prompt with the server already filled in.

    Add to Cursor
  2. 2
    Sign in

    Cursor opens newtalaria.com in your browser. Sign in and choose the organisation.

  3. 3
    Ask about production

    Try: “What broke after the last deploy in Northline?”

~/.cursor/mcp.json
{
  "mcpServers": {
    "talaria": {
      "url": "https://api.newtalaria.com/mcp"
    }
  }
}

Prefer a file? Paste this into ~/.cursor/mcp.json, or .cursor/mcp.json to share it with the repo.

OAuth

How sign-in works.

Standard OAuth 2.1 with dynamic client registration and PKCE (S256). You approve once per client.

01

Add the URL

Your client calls https://api.newtalaria.com/mcp and finds Talaria’s sign-in through the protected-resource metadata.

02

Sign in to Talaria

The browser opens newtalaria.com. The client registers itself and uses PKCE, so no secret leaves your machine.

03

Choose what it can do

Pick the organisation and access: read only, read and write, or with keys. A scoped URL narrows it further.

04

Revoke any time

Every grant is listed in Settings › Integrations › MCP with its client, scope and last use.

Scopes

Write includes read; keys includes write. Agents ask before any write, and each tool says whether it reads or writes.

mcp:readmcp:writemcp:keys

No OAuth in your client?

Create a personal token in Settings › Integrations (30 days, 90 days or until revoked) and send it as a bearer token. Never use a tal_live_ ingest key: /mcp rejects them.

Tools

40 tools, each marked read or write.

Every tool carries MCP annotations (title, readOnlyHint, destructiveHint), so clients can auto-approve reads and ask before writes.

ReadreadOnlyHint: trueWritechanges data · agents ask firstKeysneeds mcp:keysComing soonarrives with GitHub and releases

Docs3

  • docs_listRead
  • docs_searchRead
  • docs_getRead

Account2

  • get_connectionRead
  • switch_organizationRead

Projects8

  • get_projectsRead
  • get_projectRead
  • get_project_statsRead
  • update_project_settingsWrite
  • create_projectWrite
  • setup_projectWrite
  • send_test_eventWrite
  • create_api_keyKeys

Issues7

  • search_errorsRead
  • get_errorRead
  • search_eventsRead
  • get_eventRead
  • get_suspect_commitsComing soonRead
  • update_issue_statusWrite
  • add_issue_commentWrite

GitHub3

  • get_issue_linksComing soonRead
  • create_github_issueComing soonWrite
  • link_github_issueComing soonWrite

Releases3

  • list_releasesComing soonRead
  • get_releaseComing soonRead
  • verify_fixComing soonRead

Traces and replays7

  • search_tracesRead
  • get_traceRead
  • list_suspect_spansRead
  • list_database_queriesRead
  • get_replayRead
  • search_sessionsRead
  • get_logsRead

Source2

  • get_source_mapRead
  • get_source_contextRead

Flags and monitors5

  • list_feature_flagsRead
  • get_feature_flagRead
  • set_feature_flag_offWrite
  • set_feature_flag_percentWrite
  • list_monitorsRead
Scoped URLs

Give each agent only what it needs.

Scope by organisation or project, drop the write tools, or pick toolsets. Combine them freely.

https://api.newtalaria.com/mcp

Every organisation you belong to. Use switch_organization to move.

https://api.newtalaria.com/mcp/talaria-labs

One organisation. Tokens made here can’t be used on other orgs.

https://api.newtalaria.com/mcp/talaria-labs/northline

One project. Discovery tools are hidden; the agent starts in Northline.

https://api.newtalaria.com/mcp?readonly=true

Only read tools are listed. Works with any of the URLs above.

https://api.newtalaria.com/mcp?toolsets=issues,traces

Only these groups, to keep the agent’s context small.

Read only for review agents

Give a code-review bot ?readonly=true. It can read errors, traces and replays but can’t resolve, comment or change flags.

Bound to the URL

A grant made on a scoped URL only works on that URL. Widening the scope means signing in again, so a leaked token can’t reach other projects.

Questions about MCP

Do I need an API key?

No. Clients that support OAuth sign in through the browser. For clients that don’t, create a personal token in Settings › Integrations. Ingest keys (tal_live_…) never work on /mcp.

Can the agent change things in production?

Only with write access, and only through tools marked Write: resolving an issue, commenting, changing project settings or a feature flag. Clients ask before running them. Use ?readonly=true to remove them.

Which data does the agent see?

What your Talaria user can see in the organisation or project you chose. Scrubbed fields stay [Filtered]; replays come back as summaries, not recordings.

How do agents fix and verify an issue?

They read the issue with get_error and the trace with get_trace, then open a PR that says “Fixes NORTH-4F2”. Once the release ships, search_events with the issue id shows whether it is still firing. One-step fix verification (verify_fix) is coming soon.

Which clients work?

Any MCP client that speaks Streamable HTTP: Cursor, Claude Code, Codex, VS Code, Grok Bot, Windsurf and Gemini CLI. The docs have a page for each.

How do I revoke access?

Settings › Integrations › MCP lists each grant with its client, scope and last use. Revoke one and that client must sign in again.

Connect your agent, then watch it fix and verify.

Developer is $5 per month. Add Talaria to your client, sign in, and ask what broke.

Start for $5
MCP docsHow MCP works