MCP — the Model Context Protocol — is the open standard Anthropic introduced in late 2024 for letting an AI agent talk to an outside tool: read real data from it, trigger real actions in it, instead of guessing. Plenty of software now ships a server for it, but "ships MCP support" means different things depending on who built the bridge. We checked nine products spanning dev tools and creative software for exactly that: who built it, what it actually connects to, and what's still community-only.
At a glance
| Tool | Status | Connects to |
|---|---|---|
| GitHub | Official | Repos, PRs, issues, CI/CD |
| Linear | Official | Issues, projects, cycles |
| Sentry | Official | Errors + Seer AI diagnosis |
| Stripe | Official | Payments, refunds, subscriptions |
| Zapier | Official | 9,000+ connected apps |
| Unity | Official | Editor, scenes, assets, builds |
| Unreal Engine | Community | Editor via Remote Control API |
| Blender | Community | Scene via Python API |
| Photoshop | Community | Layers/scripting via a local bridge |
GitHub — repos, PRs, and issues
GitHub's own MCP server went to public preview in April 2025 as a Go rewrite of Anthropic's original reference server, and GitHub has owned its development since. Capabilities are grouped into toolsets you enable individually — code search and commit history, PR review and issue triage, CI/CD run status, Dependabot and security alerts, discussions and notifications. Connect to the hosted endpoint at api.githubcopilot.com/mcp with a one-time OAuth login, or run it locally with Docker using a personal access token.
Built and maintained by GitHub itself, not a third party — the toolset model also means you only turn on the access an agent actually needs.
The local Docker path needs a scoped personal access token managed carefully; the hosted OAuth route is the lower-friction default for most setups.
A dev team that wants an agent to triage issues and review PRs against the real state of a repo.
Linear — issues and projects, no API key to manage
Linear's server is hosted at mcp.linear.app/mcp — nothing to install or run yourself — and built in partnership with Cloudflare and Anthropic. It authenticates entirely through OAuth 2.1 in the browser, so there's no key to issue or leak. Tools cover creating and updating issues from natural language, searching by status, assignee, or label, and managing projects and cycles; issues even carry a branchName field so a coding agent can check out the right branch on its own.
Centrally hosted and OAuth-only — there's no local server to run and no API key to rotate or accidentally commit.
Hosted-only means no self-hosted option if your security policy requires keeping the server on your own infrastructure.
A product or eng team that wants an agent filing and updating issues without touching an API key.
Sentry — errors plus an AI root-cause agent
Sentry hosts its server at mcp.sentry.dev/mcp with OAuth 2.1 authentication — again nothing to install. Tools are grouped into core access (organizations, projects, teams, issues), analysis (searching errors across the codebase, investigating a specific issue), and the standout: a bridge into Seer, Sentry's own AI root-cause agent. Through MCP you can trigger a Seer analysis, get back a suggested fix with the traces and logs behind it, and check on its status, all without leaving your coding agent.
The Seer integration is a real differentiator — it hands off to a dedicated diagnostic AI instead of just forwarding raw error data.
Seer's depth depends on your Sentry plan, and Sentry itself describes the MCP server as production-ready but still evolving.
An on-call engineer who wants an agent to investigate a production error and propose a fix without switching to the dashboard.
Stripe — payments without handing over a full-access key
Stripe runs a hosted endpoint at mcp.stripe.com, plus a local @stripe/mcp package if you'd rather run it yourself — the underlying Agent Toolkit also plugs into OpenAI's Agent SDK, LangChain, CrewAI, and Vercel's AI SDK, not just MCP. Interactive clients authenticate over OAuth; autonomous agents instead pass a restricted API key as a bearer token, and admins turn MCP access on separately for sandbox and live mode. One date worth flagging: starting October 31, 2026, Stripe stops accepting full-access or older untagged restricted keys on its MCP server.
Hosted or local, and the restricted-key model keeps an agent from getting broader account access than the task needs.
If you're already connected with an old-style key, the October 31, 2026 cutoff is a real action item — check docs.stripe.com/mcp for the current key format.
A finance or support team automating refunds, subscription lookups, or payment troubleshooting without a full-access key.
Zapier — a gateway to 9,000+ other apps
Zapier's server is shaped differently from the rest of this list: instead of one product, it's a gateway to the apps Zapier already connects — more than 9,000 apps and 40,000+ actions by Zapier's own count. You create a server per AI client at mcp.zapier.com, and choose in your account which specific actions are exposed, so an agent doesn't get your whole automation library by default. It only supports Streamable HTTP, not SSE, and works from Claude, ChatGPT, Cursor, VS Code, and several others.
The only entry here that's a gateway to thousands of other tools at once, instead of one product.
Breadth over depth — for any single app on this list, that app's own dedicated server will expose more than Zapier's generic action layer.
A no-code team that wants one MCP connection instead of wiring up a dozen individual servers.
Unity — the one engine with an official server
Unity ships its own MCP package, documented at docs.unity3d.com as com.unity.ai.assistant, connecting agents like Claude Code and Cursor straight into the Editor. A bridge starts automatically when Unity opens over a local IPC channel, and a relay binary installed to ~/.unity/relay/ runs as the actual MCP server process your client launches. Through it, an agent reads real project state instead of guessing — Unity's own example is asking which components sit on a player object and getting the answer from the live scene — and can drive scene building, asset handling, lighting, and build settings in natural language.
First-party, and it reads actual project and scene state rather than inferring it — covers editor automation end to end.
Still young: Unity's own blog frames this as a 2026 addition, and a reported governed-access "AI Gateway" wasn't confirmed as shipped as of this writing.
A Unity developer who wants an agent to answer questions about the live scene and handle editor busywork.
Unreal Engine — community-built, Epic hasn't shipped one
Epic has no official MCP server for Unreal Engine. What exists is community-built, and the two most-cited projects take different approaches. ChiR24's TypeScript server drives the editor through Unreal's built-in Remote Control API — asset management, actor control, and level management on Unreal 5.0–5.6 with the right plugins enabled. A separate project pairs a C++ plugin running a TCP server inside the editor with its own Python MCP server, needing Unreal 5.5+ and Python 3.12+.
Both let an agent control the editor via natural language today, without waiting on Epic.
Community-maintained means no vendor support line — review the code before giving it editor access, the same as any third-party plugin.
An Unreal developer comfortable vetting open-source tooling who wants agent control now rather than waiting on Epic.
Blender — the de facto community standard
The most widely used option is ahujasid/blender-mcp, which pairs a Blender addon with a Python MCP server exposing Blender's own Python API to an agent over a socket connection — scene manipulation, viewport screenshots, and arbitrary Python execution, plus asset downloads from Poly Haven, Sketchfab, Hyper3D, and Hunyuan3D. It needs Blender 3.0+ and Python 3.10+, installs via the uv package manager, and LM Studio ships native support for it. Several other community servers exist too, including a Rust rewrite and an addon exposing 50+ tools over HTTP, so the right pick depends on whether you want scene control or script execution.
Mature enough to be the de facto default, and it works across multiple clients — Claude Desktop, Claude Code, LM Studio.
No backing from the Blender Foundation, so updates and security review are on the community, not a vendor — and arbitrary Python execution is a real capability to scope carefully.
A Blender artist or technical director who wants an agent to inspect or drive a scene through Python, not just generate static assets.
Photoshop — no confirmed Adobe server, several unofficial ones
No Adobe-published MCP server for Photoshop turned up in research — the closest Adobe-branded hit was an npm package aimed at a different problem (Photoshop calling out to an LLM, not an agent calling into Photoshop), and it's unconfirmed as Adobe's own. What's actually in use is third-party: a Python-API-based server (Windows only, needs Photoshop installed locally) is the most widely listed, alongside a cross-platform server that drives Photoshop through AppleScript, PowerShell, and a UXP plugin, and at least one project bundling Photoshop with Premiere Pro, Illustrator, and InDesign under one server.
Cross-platform options exist if you need macOS as well as Windows, and one project covers the whole Creative Suite, not just Photoshop.
No official Adobe server means no guarantee of staying in sync with Creative Suite updates — verify any "unified Creative Suite" claim against developer.adobe.com before trusting it.
A designer scripting repetitive Photoshop tasks who's comfortable running a local, unofficial bridge.
Official vs. community: what the label actually means
"Official" means the vendor builds, hosts or ships, and maintains the server — GitHub, Linear, Sentry, Stripe, Zapier, and Unity all fall here, and it's generally the safer default: security review, update cadence, and support are the vendor's job. "Community" means someone outside the company built it, usually because the vendor hasn't yet — true for Unreal Engine, Blender, and Photoshop right now. Community servers are often fully capable, sometimes the only option, but the maintenance and security review are on you: read the source before installing, scope any API key or token to the minimum the task needs, and don't assume a community project will track a vendor's next API change.
Will Unreal Engine, Blender, or Photoshop get official MCP servers?
Nothing confirmed as of this writing. Unity shipping its own suggests other engine and creative-tool vendors could follow, but for now those three are community-only.
Is a community MCP server safe to install?
It can be, but you're trusting a third party's code with real access to your project or account. Review what it actually does, scope any credentials tightly, and prefer an actively maintained project over an abandoned one.