MCP is Model Context Protocol. It is an open way for an AI assistant to talk to a product with your login — read data, take actions — without a developer writing a custom integration. The directory records MCP support from public docs. That is not a claim the server is official, supported, or production-ready.

MCP readiness checker

Q: How do I share this?

Use Copy summary for a plain-text list with links, or Copy link to put the stack in the page URL as #tools=slug,slug. Anyone with the link sees the same tools. Nothing is stored on our servers. The link is hash-only so caches cannot mangle it.

Add the tools you already run. The checker sorts them into agent-ready (the directory recorded MCP support from public docs), developer-wired (a public API, but someone has to build the connection), and no connection (manual only).

MCP is Model Context Protocol: an open way for an AI assistant to use a product with your login. This is a read of the Work Insiders directory flags, not a live vendor probe. The value is mostly in the NOs — those are the dead ends, with up to three MCP-ready swaps in the same category.

MCP readiness checker

MCP is Model Context Protocol — an open way for an AI assistant to use a product with your login. Add the tools you already run. The checker splits them into agent-ready, developer-wired, and no connection. The NOs are the point.

Add a tool from your stack

Search tools

Directory listings, not a vendor survey. The MCP flag means the directory recorded MCP support from public docs. It is not a claim the server is official, supported, or production-ready.

Agent-ready share

0 of 0 tools in your stack are agent-ready

0Agent-ready · MCP

0Developer-wired · API only

0No connection

Flags are from each Work Insiders listing, not a live vendor probe. Browse every MCP listing in the directory → Building a $0 stack instead? $0 stack builder → Estimating cost? Stack cost estimator →

How the check is built

Every published listing in the directory, recruiting and HR. AI-agent listings stay out.
MCP and API flags are the ones on each tool page, taken from public vendor docs at last check.
Agent-ready means the MCP flag is on. Developer-wired means the API flag is on and MCP is off. No connection means both are off.
Dead-end rows suggest up to three MCP-ready listings that share the tool’s first category, A to Z, skipping tools you already picked.

What it does not include

A 0–100 score or a letter grade. Third-party MCP wrappers, Zapier, or Make recipes. Whether your tenant actually has MCP enabled. Whether a vendor’s MCP is official, supported, or production-ready. For a $0 stack, use the $0 stack builder. For starting prices, use the stack cost estimator. To browse every MCP listing, use the MCP-filtered directory.

Frequently asked questions

What is MCP?

MCP is Model Context Protocol. It is an open way for an AI assistant to talk to a product with your login. The directory records MCP support from public docs. That is not a claim the server is official, supported, or production-ready.

Is an API good enough?

An API is for a developer. An MCP is for an AI assistant. If the tool is developer-wired, someone still has to build the connection. That can be enough if you have engineering time. It is not the same as agent-ready.

Why does my tool say no when the vendor announced MCP?

The flag comes from public docs at last check. If a vendor has shipped an MCP since we last looked, tell us and we will re-check.

How do I share this?

Use Copy summary for a plain-text list, or Copy link to put the stack in the page URL as #tools=slug,slug. Anyone with the link sees the same tools. Nothing is stored on our servers. The link is hash-only so caches cannot mangle it.