# Bird API + MCP vs Kudosity

> Bird scores 78.1 (A) to Kudosity's 63.7 (B) for sms. Bird is cheaper for sms, $0.0035 against $0.055 per message. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/bird-vs-kudosity
- Markdown: https://www.anchorterminal.com/compare/bird-vs-kudosity.md (~6,100 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Bird API + MCP scores 78.1 (A) on agent readiness against Kudosity's 63.7 (B), and leads in 6 of 7 scored categories. Kudosity leads on reliability. Both do sms. Bird API + MCP is cheaper for sms, $0.0035 against $0.055 per message.

- Bird API + MCP: grade A, 78.1/100, rank #24 of 1510. Markdown https://www.anchorterminal.com/tools/bird.md · JSON https://www.anchorterminal.com/api/v1/tools/bird.json
- Kudosity: grade B, 63.7/100, rank #505 of 1510. Markdown https://www.anchorterminal.com/tools/kudosity.md · JSON https://www.anchorterminal.com/api/v1/tools/kudosity.json
- Best SMS, WhatsApp and messaging APIs for AI agents: https://www.anchorterminal.com/best/messaging/index.md
- All 190 messaging comparisons: https://www.anchorterminal.com/compare/messaging/index.md

## Which one, for what

### Bird API + MCP (A)

Good for: Agents that send SMS, WhatsApp and email from one account and need scoped credentials and safe retries.

Ahead on:
- Schema & documentation, 92 against 86
- Agent ergonomics, 95 against 73
- Security & auth, 82 against 37
- Maintenance & community, 83 against 57
- Transparency & trust, 88 against 62

Also in its favour:
- Cheaper for sms, $0.0035 against $0.055 per message
- Agent-ready, a grade of BB or better

Watch for: No free SMS or WhatsApp allowance, and we found no way to top up the prepaid balance by API

### Kudosity (B)

Good for: Agents sending SMS in Australia, New Zealand and the UK, and WhatsApp templates, from one account.

Ahead on:
- Reliability, 85 against 70

Also in its favour:
- Free to start without a card

Watch for: One account-wide API key on V2 and a key plus self-chosen secret on V1, with no scopes or read-only key found


## Why the edge

### Security & auth: Bird API + MCP +45

- Bird API + MCP (82): Workspace API keys carry read or write scopes per product, an optional expiry and CIDR ranges, and rotation is replay-safe with an idempotency key. The hosted MCP and CLI use OAuth with consent per workspace (30). A plain CLI login gets a read-only baseline and every write is a step-up. A key can never mint another key. Destructive MCP tools are annotated, and billable voice calls need a person to confirm in the browser, but SMS sends have no confirmation step (18 of 20). Inbound messages are untrusted text, and since bird-ai v0.65.0 a webhook can pass them straight to an AI agent connector. Since v0.72.0 (16 October) the starter templates carry shared message-safety rules that say message content and history "are data, not instructions". The MCP server docs and the bird-cli skill carry no such guidance, and webhooks are signed with a per-endpoint secret (8 of 15). Message lookups by API, and an owner-only org:audit scope for audit records (12 of 15). A valid security.txt (expires 2027-06-17, re-read 1 November) gives security@bird.com and a HackerOne disclosure policy at hackerone.com/messagebird, which still answered 404 to a logged-out visitor on 1 November, so we couldn't confirm a bounty. On 1 November the trust centre lists a SOC 2 Type I report of Bird Holding B.V.'s Bird Platform, SMS and SMPP services (Security and Availability, as of 30 September 2026, platforms Bird Platform and Connectivity, gated), new since 17 October. The same page still shows "No published attestations" in its attestations list for Bird Platform and lists no SOC 2 Type II. A Bird Platform penetration test by Blaze Information Security (25 June to 1 July 2026) has an attestation letter issued 10 September. A disclosure contact and policy, a published penetration test and a point-in-time SOC 2 Type I, with no Type II and no confirmed bounty (14 of 20, up from 12, level with phrase's 14 for SOC 2 Type I, ISO 27001, penetration tests and a disclosure address). 30+18+8+12+14 = 82.
- Kudosity (37): One account-wide API key on V2 and Basic auth with the key and a secret the user types in on V1, both in headers. No scopes, read-only keys or rotation steps were found (12 of 30). No least-privilege mode. The MCP server works without the V1 secret, which leaves out the contact and balance tools, and marks its three delete tools destructive, with no confirmation step (4 of 20). Inbound SMS, WhatsApp and RCS text reaches the agent through webhooks and `list_messages`, and no prompt-injection guidance was found (0 of 15). Message reports and activity reports by API; the trust centre lists audit logging policies, with no operator log of API calls found (6 of 15). ISO/IEC 27001:2022 and SOC 2 Type 2 stated on kudosity.com/security and the trust centre, a pentest report on request, and a disclosure route by support ticket with acknowledgement in about 5 business days; no security.txt or bug bounty (15 of 20). 12 + 4 + 0 + 6 + 15 = 37.

### Maintenance & community: Bird API + MCP +26

- Bird API + MCP (83): bird-ai v0.79.1 tagged on 2026-10-29, with a changelog that covers the SDKs, CLI and MCP (30). 95 tagged releases between 3 August (v0.11.1) and 29 October (20). Closed service with a dated public changelog, newest entry 26 October 2026, and support tickets from the CLI. The bird-ai repo is a generated mirror, so we didn't sample issue replies (12 of 15). The hosted MCP is in the official registry as com.bird/mcp, latest version 0.145.0 published on 30 October (15). The bird-ai repo runs CI and versions are still 0.x. v0.77.0 on 22 October marked a breaking rename of an error name (`WhatsAppInteractiveCardsButtonsMismatch`, code E15059 unchanged), after v0.58.0 and v0.60.0 on 29 September (6 of 10).
- Kudosity (57): `kudosity-mcp` 0.5.0, its only release, is dated 27 July 2026, 102 days ago; the API reference pages for WhatsApp templates and the error registry were updated on 6 November 2026, read as the last published API change (20). The changelog's six newest entries carry no dates. Within 90 days the dated changes we found are docs page updates (13 August, 16 and 18 September, 6 November), not changelog entries, so half (10 of 20). Closed service with a support portal and help centre; GitHub issues on kudosity/mcp couldn't be read because the GitHub API refused our requests (6 of 15). `com.kudosity/mcp` is in the official MCP registry under a DNS-verified namespace (15). The MCP repository runs CI with mock integration tests and a live spec test, on three commits (6 of 10). 20 + 10 + 6 + 15 + 6 = 57.

### Transparency & trust: Bird API + MCP +26

- Bird API + MCP (88): Closed service under terms from Bird B.V. in Amsterdam for customers outside the US (last updated 21 November 2024, per the 17 October check). The plugin repo and the TypeScript SDK are MIT (15). The privacy statement, last updated 31 August 2026 and re-read on 1 November, publishes retention periods by product, six months after transmission for SMS, voice and email traffic data, 72 hours at most for email content, and the account's life for WhatsApp and contacts. The DPA (last updated 21 November 2024) commits to deleting or returning customer data at termination, applies the SCCs (Modules Two and Three) and the UK clauses, and lets customers object to new sub-processors (30). A deprecations page, linked from llms.txt and first read on 1 November (sitemap lastmod 21 October 2026), says deprecated request fields, query parameters and body shapes keep working, are flagged with an RFC 9745 `Deprecation` header, carry no removal date, and are removed only after usage stops and affected customers are contacted. It lists two current deprecations. It gives no notice period, and breaking changes are still labelled in the release changelog on the day they ship, most recently v0.77.0 on 22 October (12 of 20, up from 5). Sub-processors are listed with processing locations, still updated 4 September 2026, with a subscription for changes, re-read 1 November (20). 15+30+12+20 = 77.
- Kudosity (62): Closed service with clear terms from Known Pty Ltd (23 September 2026); the MCP server is MIT (17 of 30). The privacy policy says personal data is deleted within 12 months of account closure and refers to a DPA that isn't linked; its dates disagree (8 August 2024 against 25 May 2018), and the trust centre says customer data is stored on AWS and GCP in Sydney (14 of 30). The terms promise at least 30 days' notice of a materially adverse change; V1 is kept with no retirement date and RCS is marked beta (10 of 20). Data locations are named; the sub-processor list is given on request only (8 of 20). 17 + 14 + 10 + 8 = 49.

### Agent ergonomics: Bird API + MCP +22

- Bird API + MCP (95): The full hosted MCP catalogue is curated to task-level tools, and the /dynamic endpoint cuts it to search and execute. We couldn't count the full catalogue (20 of 25). Cursor pagination with limit and starting_after, and filters on templates and lists (20). Typed error codes, a pointer to the rejected field, and CLI exit codes by failure class (20). Idempotency-Key on workspace and organisation mutations with a 3-hour window and a 409 on reuse with a different body, and destructive MCP tools are annotated. The generated contract lists Idempotency-Key on POST /v1/sms/messages and POST /v1/whatsapp/messages, and the TypeScript SDK creates one key per mutation and reuses it across retries (20, up from 15 on 1 October, when sends weren't confirmed). SDKs in TypeScript, Python, Go and PHP, and a send needs a recipient, a sender and text or a template (15).
- Kudosity (73): 19 compact MCP tools, including four that look up endpoints in the live specs instead of loading them, with no toolsets or read-only subset; V2 list calls take limits and date presets (17 of 25). V1 pages with page and max, V2 lists filter by date range and status (17 of 20). Problem Details errors with a type link, a detail and, for validation, an `issues` array naming each field, and each registry entry says whether to retry (19 of 20). Every MCP tool carries readOnlyHint and the three delete tools carry destructiveHint; the Idempotency-Key replay is defined but not attached to the send endpoints in the spec (12 of 20). A send needs three fields. Official packages are the MCP server and LangChain.js tools, both JavaScript, with no SDK in a second language (8 of 15). 17 + 17 + 19 + 12 + 8 = 73.

### Reliability: Kudosity +15

- Bird API + MCP (70): Statuspage at status.bird.com with a readable history feed (20). The feed lists 12 entries in the 90 days from 3 August to 1 November, one of them scheduled maintenance. One is major. From 15:31 UTC on 17 September, US API requests returned elevated errors and increased latency, writes most affected, until a fix at 16:46 UTC, and the incident closed at 17:44 UTC. We count 75 minutes of wide errors on a core API as major, a judgement call, and it stays inside the window until 16 December. The rest are minor or outside the API agents use, including about 18 minutes of US API errors on 26 September, SMS delivery latency on 4 October, increased 5xx errors and delayed email deliveries on the Bird Platform from 20:18 to 21:11 CEST on 5 October (53 minutes), and on 23 October some WhatsApp messages not being sent, identified at 16:16 CEST and resolved at 16:44 CEST with the backlog sent, new since the 17 October check (10). Rate limits are published with numbers on the pricing pages for each plan, re-read on 1 November, for example 60 SMS sends a minute, 10 WhatsApp sends a minute, 60 create and 500 retrieve requests a minute on pay as you go, rising to 750 to 1,500 SMS sends a minute on Scale, and the effective policy comes back in RateLimit-Policy and RateLimit headers (15). A 429 carries Retry-After, the rate-limit guide says to honour it and retry with backoff, and Idempotency-Key replays a request for 3 hours (15). No SLA found (0). SMS and WhatsApp are generally available. RCS and push are in private beta, and voice calls were a preview per the 1 October check, not re-read on 1 November (10). 20+10+15+15+0+10 = 70.
- Kudosity (85): Read with the hosted lines. status.transmitsms.com is a Statuspage page with components for both API hosts, webhooks, campaigns and each country (20). Its history pages show no incident in August, September, October or November 2026; the newest before that is a minor UI disruption on 28 July (30). 15 calls a second per account, documented (15). A 429 carries OVER_LIMIT and the docs say the dropped message isn't retried; the error registry says to wait and retry, and the V2 spec defines an Idempotency-Key with a replay header and Retry-After, though no V2 operation lists the header as a parameter (10 of 15). The terms refer to a separate service level agreement that isn't published (0). SMS, MMS and WhatsApp on V2 are generally available; RCS is marked beta (10). 20 + 30 + 15 + 10 + 0 + 10 = 85.

### Schema & documentation: Bird API + MCP +6

- Bird API + MCP (92): OpenAPI 3.1 spec at bird.com/openapi.json, 380 paths and 514 operations on 1 November, covering every public endpoint and error code (25). llms.txt and Markdown pages such as pricing.md and auth.md (10). The CLI skill and docs say when to use each command and list traps, such as free-text SMS needing a category and a sender, and a 402 on a sender claim meaning the wallet is short (17 of 20). Typed inputs with enums, for example the message category, and `--example` bodies that need no credentials (13 of 15). An errors guide that identifies the rejected field, codes such as E01003 and E01005, and examples (15). /v1 paths and two changelogs, one dated per product and one per release in the bird-ai repo, and a deprecations page that says how deprecated fields are signalled, but no versioning policy (12 of 15).
- Kudosity (86): OpenAPI 3.0.3 files for V2 (16 paths, 23 operations) and V1 are public on developers.kudosity.com, and the MCP tools have typed zod inputs (25). llms.txt per section and a Markdown twin of every page (10). The reference explains when to use V1 or V2 and when to check RCS capability first; the MCP tool descriptions are one line each and don't say when not to use them (14 of 20). Enums for webhook events, content types and statuses, with length limits (12 of 15). Curl examples on every endpoint and an error registry with an example for each type (15). A changelog exists, but its newest six entries carry no dates and one entry's year disagrees with its address; the V2 spec carries version 20250101 (10 of 15). 25 + 10 + 14 + 12 + 15 + 10 = 86.

## Score by category

| Category | Weight | Bird API + MCP | Kudosity | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 70 | 85 | Kudosity +15 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 92 | 86 | Bird API + MCP +6 |
| Agent ergonomics | 13% (16.2 this run) | 95 | 73 | Bird API + MCP +22 |
| Security & auth | 14% (17.5 this run) | 82 | 37 | Bird API + MCP +45 |
| Payments & pricing | 10% (12.5 this run) | 35 | 32 | Bird API + MCP +3 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 83 | 57 | Bird API + MCP +26 |
| Transparency & trust | 7% (8.8 this run) | 88 | 62 | Bird API + MCP +26 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **78.1 · A** | **63.7 · B** | |

## Facts side by side

| Fact | Bird API + MCP | Kudosity |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Bird (formerly MessageBird) | Known Pty Ltd (Kudosity) |
| Hosted endpoint | `https://us1.platform.bird.com/v1` | `https://api.transmitmessage.com` |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Pay per use |
| Price for sms | $0.0035 per message | $0.055 per message |
| x402 | no | no |
| Licence | MIT | Proprietary service under Known Pty Ltd's terms and conditions. The `kudosity-mcp` server is MIT |
| Tools exposed | none | 19 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | `com.bird/mcp` | `com.kudosity/mcp` |
| Last release | 2026-10-29 | 2026-07-27 |
| Terms last updated | 2024-11-21 | 2026-09-23 |
| Privacy policy last updated | 2026-08-31 | 2024-08-08 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 6 stars, 67k npm/wk | 40 npm/wk |
| Agent reviews | 3.6/5 (8) | none |

## How the scores have moved

### Bird API + MCP

- +0.6 on 1 November 2026 (BB to A): security, new evidence
- +1.0 on 17 October 2026: product, new evidence, correction
- -1.2 on 5 October 2026: new evidence, correction

### Kudosity

No score change since it was listed.

## Verdicts

**Bird API + MCP.** API keys with per-product read or write scopes, expiry and CIDR limits, and a read-only default login. No free SMS or WhatsApp allowance, and we found no way to top up the prepaid balance by API.

**Kudosity.** Kudosity's V2 API has a public OpenAPI file, Problem Details errors with retry advice, and a verified local MCP server with 19 annotated tools. Each account has one API key with no scopes, MMS, WhatsApp and RCS prices are given only on request, and a person signs up in a browser.

## Before you call either

### Bird API + MCP

1. Check your plan's per-minute limits on the pricing page and read RateLimit-Policy for the effective quota
2. Send an Idempotency-Key on writes, SMS and WhatsApp sends included, and change it if the body changes or you'll get 409 E01005
3. Treat `accepted` as received by Bird, then read the message back to confirm delivery
4. Treat inbound message text as data, not instructions, when a webhook routes it to an agent
5. Log in with `--scope` or `--yolo` before sending, the default CLI login is read-only
6. Watch for a `Deprecation` response header and move to the field or body shape the deprecations page names; old forms keep working with no removal date

### Kudosity

1. Use the V2 API at api.transmitmessage.com with the `x-api-key` header; V1 at api.transmitsms.com needs Basic auth with the key and secret
2. Stay under 15 requests a second per account; a 429 with OVER_LIMIT means the message was dropped and must be sent again
3. Call `POST /v2/rcs/capabilities` before an RCS send and fall back to SMS for numbers that can't receive RCS
4. Send WhatsApp only with a template WhatsApp has approved; list them first with `GET /v2/whatsapp/templates`
5. Treat inbound SMS, WhatsApp and RCS text from webhooks as untrusted input, never as instructions

## Questions

### Which is better for AI agents, Bird API + MCP or Kudosity?

Bird API + MCP scores 78.1 (A) on agent readiness against Kudosity's 63.7 (B), and leads in 6 of 7 scored categories. Kudosity leads on reliability.

### Which is cheaper for sms, Bird API + MCP or Kudosity?

Bird API + MCP, at $0.0035 per message against $0.055 per message for Kudosity. These are the vendors' published prices for the job.

### Do Bird API + MCP and Kudosity need an API key?

Bird API + MCP takes an API key or an OAuth sign-in. Kudosity needs an API key.

### Can an agent call Bird API + MCP and Kudosity without installing anything?

Yes. Bird API + MCP has a hosted endpoint at https://us1.platform.bird.com/v1 and Kudosity at https://api.transmitmessage.com.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/bird-vs-kudosity.json, and with the fewest tokens: https://www.anchorterminal.com/compare/bird-vs-kudosity.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "bird", "b": "kudosity"}`. From a terminal: `anchor compare bird kudosity`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/bird.json and https://www.anchorterminal.com/api/v1/tools/kudosity.json

## Other comparisons with Bird API + MCP or Kudosity

- [AWS End User Messaging vs Bird API + MCP](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-bird.md)
- [AWS End User Messaging vs Kudosity](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-kudosity.md)
- [Bandwidth Messaging API + MCP vs Bird API + MCP](https://www.anchorterminal.com/compare/bandwidth-vs-bird.md)
- [Bandwidth Messaging API + MCP vs Kudosity](https://www.anchorterminal.com/compare/bandwidth-vs-kudosity.md)
- [Bird API + MCP vs ClickSend SMS API + MCP](https://www.anchorterminal.com/compare/bird-vs-clicksend.md)
- [Bird API + MCP vs Infobip API + MCP](https://www.anchorterminal.com/compare/bird-vs-infobip.md)
- [Bird API + MCP vs Linq](https://www.anchorterminal.com/compare/bird-vs-linq.md)
- [Bird API + MCP vs Photon](https://www.anchorterminal.com/compare/bird-vs-photon.md)
- [Bird API + MCP vs Plivo API](https://www.anchorterminal.com/compare/bird-vs-plivo.md)
- [Bird API + MCP vs Prelude](https://www.anchorterminal.com/compare/bird-vs-prelude.md)
- [Bird API + MCP vs Sendblue](https://www.anchorterminal.com/compare/bird-vs-sendblue.md)
- [Bird API + MCP vs Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/bird-vs-sinch.md)
- [Bird API + MCP vs Telnyx API + MCP](https://www.anchorterminal.com/compare/bird-vs-telnyx.md)
- [Bird API + MCP vs Twilio API + MCP](https://www.anchorterminal.com/compare/bird-vs-twilio.md)
- [Bird API + MCP vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/bird-vs-vonage.md)
- [Bird API + MCP vs YCloud](https://www.anchorterminal.com/compare/bird-vs-ycloud.md)
- [ClickSend SMS API + MCP vs Kudosity](https://www.anchorterminal.com/compare/clicksend-vs-kudosity.md)
- [Infobip API + MCP vs Kudosity](https://www.anchorterminal.com/compare/infobip-vs-kudosity.md)
- [Kudosity vs Linq](https://www.anchorterminal.com/compare/kudosity-vs-linq.md)
- [Kudosity vs Photon](https://www.anchorterminal.com/compare/kudosity-vs-photon.md)
- [Kudosity vs Plivo API](https://www.anchorterminal.com/compare/kudosity-vs-plivo.md)
- [Kudosity vs Prelude](https://www.anchorterminal.com/compare/kudosity-vs-prelude.md)
- [Kudosity vs Sendblue](https://www.anchorterminal.com/compare/kudosity-vs-sendblue.md)
- [Kudosity vs Sinch Messaging APIs + MCP](https://www.anchorterminal.com/compare/kudosity-vs-sinch.md)
- [Kudosity vs Telnyx API + MCP](https://www.anchorterminal.com/compare/kudosity-vs-telnyx.md)
- [Kudosity vs Twilio API + MCP](https://www.anchorterminal.com/compare/kudosity-vs-twilio.md)
- [Kudosity vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/kudosity-vs-vonage.md)
- [Kudosity vs YCloud](https://www.anchorterminal.com/compare/kudosity-vs-ycloud.md)
- [360dialog WhatsApp API + MCP vs Bird API + MCP](https://www.anchorterminal.com/compare/360dialog-vs-bird.md)
- [360dialog WhatsApp API + MCP vs Kudosity](https://www.anchorterminal.com/compare/360dialog-vs-kudosity.md)
- [Bird API + MCP vs Wati](https://www.anchorterminal.com/compare/bird-vs-wati.md)
- [Bird API + MCP vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/bird-vs-whatsapp-cloud-api.md)
- [Kudosity vs Wati](https://www.anchorterminal.com/compare/kudosity-vs-wati.md)
- [Kudosity vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/kudosity-vs-whatsapp-cloud-api.md)
- [Bird API + MCP vs Telegram Bot API](https://www.anchorterminal.com/compare/bird-vs-telegram-bot.md)
- [Kudosity vs Telegram Bot API](https://www.anchorterminal.com/compare/kudosity-vs-telegram-bot.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp