MCP · the tool belt

Give your agent production truth.

Hosted MCP server with OAuth, 44 tools, and scoped URLs. Your coding agent uses these tools to run the five-skill playbook.

https://api.newtalaria.com/mcp
44 MCP toolsOAuth 2.1 · PKCEStreamable HTTPRead-only mode
Works with
CursorGrok BotVS Code + CopilotCopilot CLIClaude CodeGemini CLI
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 chat (works now)

    Ask your Bot: "Add a custom MCP server named Talaria at https://api.newtalaria.com/mcp". Confirm the URL, then Authorize and sign in to Talaria in the browser.

  2. 2
    Or search Connect apps

    Once Talaria appears in Connect apps search, open Connect apps (tap your avatar first on phone), search Talaria, add it, then Authorize.

  3. 3
    Check it's installed

    Talaria appears under Installed and works in every Bot on your account.

Chat with Grok Bot
Add a custom MCP server named Talaria at https://api.newtalaria.com/mcp

Marketplace listing with five agent skills is submitted and pending. Until it shows in Connect apps search, use the custom Add MCP message — same hosted URL and OAuth. Plugin source: github.com/newtalaria/talaria-agent-plugin. Full playbook: /docs/guides/agent-skills.

Agent skills

Skills use these tools.

The Talaria plugin brings five agent skills (the playbook) that use the MCP tools below. Available on cursor.directory/plugins/talaria (live) and Grok Bot Connect apps (marketplace pending). Read the full playbook.

Get startedtalaria-get-started
→
Instrumenttalaria-instrument
→
Observe performancetalaria-observe-performance
→
Triage an issuetalaria-triage-issue
→
Verify a fixtalaria-verify-fix
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

44 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:keys

Docs3

  • docs_listList Talaria docsRead
  • docs_searchSearch Talaria docsRead
  • docs_getRead a Talaria docs pageRead

Connection2

  • get_connectionShow MCP connectionRead
  • switch_organizationSwitch MCP organizationWrite

Projects6

  • get_projectsList projectsRead
  • get_projectGet project settingsRead
  • update_project_settingsUpdate project settingsWrite
  • create_projectCreate projectWrite
  • setup_projectSet up project for an SDK installKeys
  • send_test_eventSend test eventWrite

Keys1

  • create_api_keyCreate ingest API keyKeys

Issues10

  • search_errorsSearch issuesRead
  • get_errorGet issue with investigation packRead
  • update_issue_statusUpdate issue statusWrite
  • add_issue_commentComment on issueWrite
  • create_github_issueCreate GitHub issueWrite
  • link_github_issueLink GitHub issueWrite
  • unlink_github_issueUnlink GitHub issueWrite
  • get_issue_linksList linked GitHub issuesRead
  • verify_fixVerify a fix held after releaseRead
  • get_suspect_commitsRank suspect commitsRead

Releases2

  • list_releasesList project releasesRead
  • get_releaseGet a project releaseRead

Events6

  • search_eventsSearch eventsRead
  • get_eventGet eventRead
  • get_source_mapResolve source-mapped frameRead
  • get_replayGet session replay summaryRead
  • get_source_contextGet commit-exact source from GitHubRead
  • wait_for_eventWait for a matching eventRead

Performance4

  • search_tracesSearch tracesRead
  • get_traceGet trace waterfallRead
  • list_suspect_spansList suspect spansRead
  • list_database_queriesList database queriesRead

Analytics2

  • search_sessionsSearch sessionsRead
  • get_project_statsGet project health statsRead

Flags4

  • list_feature_flagsList feature flagsRead
  • get_feature_flagGet feature flagRead
  • set_feature_flag_offTurn feature flag offWrite
  • set_feature_flag_percentSet feature flag rollout percentWrite

Ops3

  • list_monitorsList monitorsRead
  • list_monitor_runsList monitor runsRead
  • get_logsRead logsRead

AI1

  • list_agent_runsList recent agent runsRead
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,performance

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?

The agent reads the issue with get_error, makes the fix, and — once the release ships — calls verify_fix to confirm the fix held. Dashboard AI is a separate assistant; it reads what you already stored, while MCP lets the agent investigate and verify.

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.