MCP server: a census of 143 listings

No MCP server is documented; agent-to-agent access exists via IBM's Agent Connect programme for the lead/account research agent.

Source retrieved 2026-09-03

Ada ships a hosted MCP server over Streamable HTTP with OAuth or API-key auth, exposing most dashboard operations to any MCP client.

Source retrieved 2026-10-03

MCP is the transport on the Claude side: the bridge is an MCP client loaded as a Claude Code plugin and exposes a reply tool the agent calls to push messages across.

Source retrieved 2026-10-03

MCP is engineering the firm performs for clients - it implements Model Context Protocol servers inside delivered architectures - but Agentix publishes no MCP endpoint of its own that another agent could query.

Source retrieved 2026-10-03

MCP works both ways: agents consume external MCP servers, and your tools or a live runtime can be published for other MCP hosts to query.

Source retrieved 2026-09-09

AgentOS can expose registered agents as an MCP server, so another agent can call them; docs also ship as MCP.

Source retrieved 2026-09-02

MCP is named as an inbound channel for Aide to reach your systems and pull context, not as an MCP server another agent could query; the direction of the connection is Aide reading your data.

Source retrieved 2026-09-23

A hosted MCP server at loadout.aident.ai/mcp lets any MCP-compatible client search, inspect and execute capabilities after browser OAuth, with staging and RC endpoints documented too.

Source retrieved 2026-10-03

MCP is supported in one direction only: Aisera acts as an MCP client consuming external servers' tools, capped at ten per tenant, and no MCP server endpoint is documented for another agent to query Aisera.

Source retrieved 2026-09-24

A production MCP server lets another agent search, enrich, build lists and query analytics against your account over OAuth, it is ticked on all three plan columns, and no extra fee applies.

Source retrieved 2026-09-10

It is an MCP client: local stdio and remote servers are configured globally or per workspace with per-tool approval, but no MCP server is documented that would let another agent query this CLI.

Source retrieved 2026-09-10

Every marketplace API is automatically an MCP server on a published URL pattern, with each endpoint turned into a named MCP tool and authenticated by the same key.

Source retrieved 2026-10-03

A hosted streamable-HTTP MCP server with OAuth 2.1 and PKCE exposes search, counts, previews, reveals and exports as tools another agent can call.

Source retrieved 2026-09-26

Artisan publishes an MCP server URL that exposes 30 tools to an MCP client, available on every plan and authenticated by sign-in rather than an API key, though the vendor labels the connector an early feature.

Source retrieved 2026-09-10

The AI Agents service exposes its own MCP server over streamable HTTP so another agent can create agents, run test suites and inspect conversations, with an optional read-only mode.

Source retrieved 2026-09-24

Context Engine is exposed to other agents over MCP (local stdio or hosted HTTP), and MCP tools are on both plans.

Source retrieved 2026-09-02

AutoGen consumes MCP servers as agent tools through McpWorkbench, but the docs do not describe exposing an AutoGen agent as an MCP server another agent could query.

Source retrieved 2026-09-19

Bland hosts a remote MCP server so another agent can place calls, read transcripts and manage pathways with an API key.

Source retrieved 2026-09-11

MCP runs one way only: Bolt is a client that connects out to Notion, Linear, GitHub or custom servers, and exposes no MCP server another agent could call.

Source retrieved 2026-09-11

Helpdesk operations are exposed as MCP tools for Claude Code, Claude Desktop and Cursor, and in the other direction an agent can call tools from an MCP server you configure.

Source retrieved 2026-09-02

MCP runs both ways: agents consume MCP integrations to reach connected apps, and a finished agent can itself be exposed as an MCP server that another AI system calls.

Source retrieved 2026-09-13

Hosted MCP server at mcp.browserbase.com gives MCP clients browser automation via Stagehand.

Source retrieved 2026-09-02

A hosted MCP server (mcp.cartesia.ai) exposes tools for TTS, STT, voices, cloning and credit usage to another agent.

Source retrieved 2026-09-02

The agent is a full MCP client over stdio, HTTP/SSE and in-process servers; the docs describe no way to expose your agent as an MCP server another agent could query.

Source retrieved 2026-09-02

claude mcp serve exposes Claude Code as a stdio MCP server other clients connect to; it is also an MCP client for external servers.

Source retrieved 2026-09-02

Cline is an MCP client - you attach local or remote servers to it, and a marketplace lists them - but the vendor documents no MCP server exposing Cline itself to another agent.

Source retrieved 2026-09-12

Codex is an MCP client for local and remote servers, but exposing Codex itself as an MCP server is deprecated in favour of the app server.

Source retrieved 2026-09-02

MCP runs the other way round: Crescendo's assistants act as clients against third-party MCP servers such as Shopify's, and no Crescendo MCP server is published for outside agents to query.

Source retrieved 2026-09-12

MCP is supported in the outbound direction, letting Cresta agents reach your CRM, billing and scheduling tools; nothing states that an external agent can query Cresta through an MCP server.

Source retrieved 2026-09-13

Both plans can publish a built workflow as an MCP server so other agents can call it, and agents can equally consume any external MCP server as tooling.

Source retrieved 2026-09-13

MCP is inbound only: Cursor is the client that connects to MCP servers. Another agent drives Cursor over ACP (agent acp) or the SDKs, not by querying an MCP endpoint Cursor exposes.

Source retrieved 2026-09-02

MCP is supported as the way Decagon's agent reaches your systems; no page says Decagon exposes an MCP server another agent could query.

Source retrieved 2026-09-14

Two MCP servers exist, one built into the dg CLI and an HTTP docs server, but the CLI server's published tool list is transcription, synthesis, text analysis, model listing and usage. Nothing exposes running or querying a voice agent over MCP.

Source retrieved 2026-09-02

An authenticated MCP server at mcp.devin.ai lets any MCP client create sessions, query repositories and manage playbooks.

Source retrieved 2026-09-02

Devin Desktop is an MCP client that consumes servers with per-tool approval; the server another agent can query is the Devin platform's, at mcp.devin.ai, not the desktop session.

Source retrieved 2026-09-03

Any app can be exposed as an MCP server from its Access Point tab; the URL carries credentials and can be regenerated.

Source retrieved 2026-09-02

Dust publishes a remote MCP server per region so another agent can query workspace knowledge, conversations and files over OAuth, with admins able to disable it.

Source retrieved 2026-10-01

A hosted, OAuth-authenticated MCP server lets another assistant create, edit, cost-estimate and read the transcripts of your agents; per-region URLs exist for isolated workspaces.

Source retrieved 2026-09-02

Elicit runs a hosted MCP server with OAuth 2.0 so another agent can query it directly, exposing the full API surface, but the entitlement begins at Pro rather than the free plan.

Source retrieved 2026-09-14

Both a remote streamable-HTTP server and a local stdio server expose 28 operations as tools, with OAuth or key auth, but it depends on the API access sold from Ultra upward.

Source retrieved 2026-10-03

Droid is an MCP client over stdio/http/sse and can be driven by another program over JSON-RPC or ACP, but no Factory-hosted MCP server is documented.

Source retrieved 2026-09-02

MCP runs both ways: Fin reaches business tools through MCP connectors, and an Intercom MCP server lets outside AI systems read the conversation data Fin produces.

Source retrieved 2026-09-18

An official hosted MCP server accepts OAuth sign-in, API keys or keyless daily-limited access, so another agent can query Firecrawl directly.

Source retrieved 2026-09-24

GC AI runs its own remote MCP server exposing twenty tools over OAuth, so another agent can query and act in the account; it is public beta and off until an org admin turns it on.

Source retrieved 2026-09-14

Code Assist is an MCP client, not an MCP server: agent mode connects to local and remote MCP servers in both VS Code and JetBrains, but nothing exposes Code Assist for another agent to query.

Source retrieved 2026-09-02

Another agent can start a Copilot cloud session through the remote GitHub MCP Server, on paid plans only; separately, Copilot consumes third-party MCP servers on every plan.

Source retrieved 2026-09-02

A remote Glean MCP server exposes Glean tools and agents to other AI hosts; Glean can also consume external MCP servers.

Source retrieved 2026-09-02

MCP works in both directions: agents consume external MCP servers as tools, and you can wrap ADK tools in an MCP server that any other MCP client can call.

Source retrieved 2026-09-15

goose is primarily an MCP client that consumes 70+ extensions, and its CLI can run an enabled MCP server; another agent drives goose itself over ACP rather than through a goose-provided MCP server.

Source retrieved 2026-09-16

The official gptr-mcp server exposes deep_research, quick_search, write_report and source tools over stdio, SSE and Streamable HTTP.

Source retrieved 2026-09-16

Gumloop runs a remote MCP server exposing dozens of tools so another agent can list agents, run sessions and search Company Brain; MCP is a Pro-and-above line item.

Source retrieved 2026-09-30

HOL publishes a Guard Cloud MCP endpoint over Streamable HTTP with OAuth metadata, so another agent can query it.

Source retrieved 2026-09-29

A stateless Streamable HTTP MCP server exposes three read-only tools for job and company search, unauthenticated, so another agent can query the inventory but cannot act.

Source retrieved 2026-09-14

Juggler is a full MCP client — local stdio or remote HTTP/SSE servers, header auth, per-tool allow and deny lists, and inspectable handoffs — but it publishes no MCP server of its own, so another agent cannot query Juggler this way.

Source retrieved 2026-09-17

MCP runs one way only: Junie consumes external MCP servers as a client. Another program reaches it through ACP instead, and no MCP server exposing Junie is documented.

Source retrieved 2026-09-18

Another AI can query Kalyvox through the ChatGPT connector, included from Solo, but it is read-only and scoped to authorised data categories; the vendor documents no MCP server, and its own REST API is the only other programmatic route.

Source retrieved 2026-09-26

First-class MCP client with a marketplace and private org servers.

Source retrieved 2026-09-02

Agents can be exposed as MCP servers on every plan including the free one, and can themselves consume tools from remote MCP servers; LangSmith also publishes its own MCP server.

Source retrieved 2026-09-18

Each Langflow project is exposed as an MCP server whose flows appear to clients as tools, over streamable HTTP with SSE fallback and optional API-key authentication.

Source retrieved 2026-09-25

A deployed agent can be exposed as an MCP server, so another agent can call it; the plan table checks this row on Developer, Plus and Enterprise alike.

Source retrieved 2026-09-02

MCP is the architecture rather than an add-on: the vendor states every feature ships as a tool, included on every plan including the free one, with the same credits and the same approval gate.

Source retrieved 2026-09-18

MCP runs inbound only: you point Lindy at a hosted MCP server and it builds an action per published tool, with per-connection sharing and approval settings. Lindy publishes no MCP server of its own for another agent to query.

Source retrieved 2026-09-19

The agent is the MCP client: it consumes tools from remote HTTP or local stdio MCP servers, Python only. LiveKit does not expose a running agent as an MCP server for another agent to query.

Source retrieved 2026-09-02

Hosted MCP server with OAuth exposes parse, classify, extract, split and index tools to any MCP client, in NA and EU.

Source retrieved 2026-09-02

MCP is real and native but gated: five servers from the Growth plan and unlimited on Enterprise, while the Basic and Starter cards show it struck through.

Source retrieved 2026-09-09

Manus is an MCP client (prebuilt MCP connectors on every plan plus your own custom MCP servers), but no Manus-hosted MCP server another agent could query is documented; the REST API is the way in.

Source retrieved 2026-09-19

Both directions: MCPClient consumes external MCP servers, and MCPServer publishes your agents, tools and workflows to other MCP clients over stdio or HTTP.

Source retrieved 2026-09-02

Maven supports Model Context Protocol as a client: a team pastes an MCP server URL and configures access in the UI, though the vendor routes activation through your assigned CX manager rather than open self-serve setup.

Source retrieved 2026-09-25

Another agent can reach yours over MCP or A2A, but the Python hosting packages that expose those endpoints are prerelease, and you must build and secure the server yourself.

Source retrieved 2026-09-19

You can register published agents on a MindStudio-hosted MCP server, so another LLM or agent client can invoke them as tools over an authenticated remote endpoint.

Source retrieved 2026-09-20

MCP Workspace lets admins connect remote MCP servers so the assistant can call their tools, but it is limited-availability, server-level only, and local servers are unsupported.

Source retrieved 2026-09-20

Muse Code is an MCP client — it connects stdio and streamable-HTTP servers, with OAuth sign-in — but the vendor documents no MCP server exposing Muse Code to another agent.

Source retrieved 2026-09-20

Both directions: an instance-level MCP server exposes chosen workflows to external clients, the MCP Server Trigger node turns one workflow into its own server, and the MCP Client Tool calls outside servers.

Source retrieved 2026-09-02

A remote OAuth MCP server at /mcp exposes read, edit and apply tool groups to any assistant supporting custom connectors, with per-client daily read budgets.

Source retrieved 2026-09-29

Two MCP entry points expose every REST endpoint as a tool: a hosted OAuth server and a local stdio package, so another agent can drive calls and campaigns.

Source retrieved 2026-09-09

The SDK acts as an MCP client across stdio, SSE, Streamable HTTP and hosted transports, so agents can consume MCP tools; no documentation describes exposing the SDK itself as an MCP server another agent could query.

Source retrieved 2026-09-20

A Realtime session is an MCP client that calls remote MCP servers and OpenAI connectors itself, but the vendor publishes no MCP server that would let another agent query the Realtime API.

Source retrieved 2026-09-02

MCP works both directions: OpenClaw connects to third-party MCP servers over stdio, SSE or streamable HTTP, and can itself serve as an MCP server to another client.

Source retrieved 2026-09-21

It consumes local and remote MCP servers as a client, but the vendor documents no MCP server of its own for other agents to query.

Source retrieved 2026-09-21

MCP is fully supported on CLI, SDK, local GUI and Cloud, letting the agent consume external tool servers over SSE, SHTTP or stdio.

Source retrieved 2026-09-21

Perplexity hosts a remote MCP server another agent can query with an API key, and publishes a local stdio server as an alternative.

Source retrieved 2026-09-02

Another agent can drive the workspace through a hosted MCP server at a single address, authenticating with a workspace, personal or deployment key, and can run any agent without deploying it first.

Source retrieved 2026-09-09

Builder MCP exposes build/test/deploy tools and Data MCP exposes transcripts and metrics to any MCP client; agents can also call external MCP servers.

Source retrieved 2026-09-02

MCP is supported as a client: the MCP capability connects any MCP server's tools into your agent, and the CLI takes an mcpServers config file; the docs I read establish consumption, not your agent being queried as an MCP server.

Source retrieved 2026-09-21

A hosted MCP server at mcp.relevanceai.com lets another agent list and run your agents, with OAuth access bounded server-side by the caller's project role.

Source retrieved 2026-09-22

Replit runs its own MCP server over streamable HTTP with OAuth, exposing tools that create, update and publish apps from any client.

Source retrieved 2026-09-22

Retell runs a hosted MCP endpoint authenticated with an API key, exposing agent, call, knowledge-base and QA tools so another assistant can drive the account.

Source retrieved 2026-09-23

'MCP Support' is ticked only in the Enterprise column of the plan comparison (dashes for Individual and Teams); no MCP server URL, tool list or setup guide is published in the docs.

Source retrieved 2026-09-03

MCP is central to how SafeNet builds, but as a bespoke server architected for the client in the top enterprise scope, not as a hosted MCP endpoint another agent could query off the shelf.

Source retrieved 2026-09-28

Salesforce hosts MCP servers so external agents can query an org under per-user OAuth, and Agentforce is also an MCP client consuming third-party servers attached in Agent Builder.

Source retrieved 2026-09-03

The entire product is a remote MCP server, so any MCP-capable agent can query it once OAuth consent and LinkedIn connection are in place.

Source retrieved 2026-09-25

A hosted MCP server is on every plan including Free, with OAuth or key auth, and acting tools unlocked on any paid plan rather than only the top tier.

Source retrieved 2026-10-03

Agents are exposed over MCP for the ChatGPT Apps channel; a general MCP server other agents may query is not documented publicly.

Source retrieved 2026-09-26

Two directions: workflows are published as MCP tools, and external MCP servers can be added as agent tools.

Source retrieved 2026-09-03

A hosted MCP server at one URL exposes four named review tools over OAuth, so another agent can call the scans and architecture reviews directly.

Source retrieved 2026-10-03

SkipCalls acts as an MCP client (it connects out to your MCP servers and discovers their tools), but the vendor publishes no MCP server through which another agent could query SkipCalls itself.

Source retrieved 2026-09-26

A hosted MCP server lets another assistant list, read, run and edit your workflows after an OAuth sign-in, and a MCP node lets your agents call outside MCP servers.

Source retrieved 2026-09-09

A hosted MCP server in three regions exposes agent, call and knowledge-base tools to MCP clients.

Source retrieved 2026-09-03

Tale serves its own MCP endpoint over HTTPS JSON-RPC so an external agent can discover tools, retrieve knowledge and run automations.

Source retrieved 2026-10-03

The vendor publishes an MCP server card for its own site and wires MCP servers into client agents, but the declared SSE endpoint answered HTTP 502 when I requested it on 12 September 2026.

Source retrieved 2026-09-12

TelEcho documents a native MCP integration letting an agent inside ChatGPT or Claude define and configure TelEcho agents; no server address, tool inventory or auth flow is published to verify scope.

Source retrieved 2026-09-16

MCP works in both directions: a hosted Telnyx MCP endpoint lets another agent drive the account, and external MCP servers can be attached as tools to an assistant.

Source retrieved 2026-09-09

Hosted MCP server with OAuth 2.1 exposes automation, search, fetch, browser-session and wallet tools.

Source retrieved 2026-09-03

Both directions are documented: an agent can add external MCP servers as tools, and a UiPath MCP Server exposes deployed agents and automations as tools at a URL the docs say external MCP clients connect to.

Source retrieved 2026-09-03

A hosted MCP server at mcp.undermind.ai exposes deep search, PDF reading and workspace tools, and the Free plan row already includes agent connection.

Source retrieved 2026-09-26

An official MCP server exposes the same agent as Unify Chat to external assistants, with no separate charge beyond existing credits.

Source retrieved 2026-09-27

A hosted MCP server exposes assistants, calls and numbers to another agent, and assistants can also call external MCP servers.

Source retrieved 2026-09-03

Another agent can drive Vecbase over MCP: the CLI installs MCP contracts and per-client server entries for Codex, Claude Code, Cursor, Gemini CLI, Copilot and OpenClaw.

Source retrieved 2026-09-27

Vellum is an MCP client: it connects to MCP servers added in settings or shipped by plugins, but the docs describe no MCP server through which another agent could query the assistant.

Source retrieved 2026-09-27

A remote MCP server lets any MCP client read that customer's calls, transcripts, texts and usage over OAuth, included on every plan at no extra charge, but it cannot write anything.

Source retrieved 2026-09-22

MCP is named as a mechanism for the customer's agent to reach external systems, and as a Starter plan bullet; no MCP server is documented for another agent to query, and the developer docs and OpenAPI spec never mention MCP.

Source retrieved 2026-09-03

OAuth MCP server with three read-only tools plus a credit-balance tool, callable by any MCP client.

Source retrieved 2026-09-03

Warp is a mature MCP client for local and cloud agents. Being queried by another agent works only through the hosted Factory MCP server, which is inside Warp Factories Early Access.

Source retrieved 2026-09-03

MCP is the vendor's stated default interface, letting any MCP client start a run and read back structured results without a person in the loop.

Source retrieved 2026-09-27

A first-party MCP server at xquik.com/mcp exposes 119 routes to authenticated clients, plus a separate docs MCP server, with OAuth 2.1 or an API-key fallback.

Source retrieved 2026-10-03

Zendesk is an MCP client: AI agents can call tools on external MCP servers from Suite Growth / Support Team upward. No vendor-documented MCP server exposing the AI agents to other agents.

Source retrieved 2026-09-03

MCP is deliberately absent from the binary and is framed as something to skip; reaching MCP servers requires installing a third-party bridge extension you must review and trust yourself.

Source retrieved 2026-09-28