Manufact
Product▾
- MCP HostingDeploy MCP apps and servers to production.
- Cross-client testingRun the same checks across ChatGPT, Claude, and more.
- Publishing checksAudit your MCP app against ChatGPT Apps Store and Cloud Connectors requirements.
- Submission PackGenerate the assets you need for marketplace submission.
- Cloud InspectorTrace, replay, and debug MCP traffic in production.
- Public chatEmbeddable chat surfaces for your product.
- AnalyticsUsage, latency, and reliability in one place.
- Products
- Cloud
- mcp-use SDK
- Inspector
- Vibe
Developers▾
- Manufact docsBuild, deploy, and operate on Manufact Cloud.
- SupportCommunity, issue reporting, and premium support.
- TemplatesStart from a deploy-ready MCP framework template.
- mcp-use docsBuild MCP apps and servers with the mcp-use SDK.
- mcp-use Inspector DocsInspect and debug MCP servers from your browser.
- mcp-use client CLIConnect to and call MCP servers from your terminal.
- MCP server tunnelingExpose a local MCP server through a secure tunnel.
- Pricing
- Blog
Backstage
mcp.backstage.com/mcp
Excellent
Protocol
Tools
All tools have OpenAI behavior hints
All tools declare the three OpenAI behavior hints as booleans
All tools have descriptions
All tools have non-empty descriptions
Declared output schemas have a valid basic structure
4 declared output schema(s) pass basic structural validation; schemas may describe any JSON value, including arrays
Tool input header annotations are valid
All x-mcp-header annotations satisfy Streamable HTTP requirements
Tool input schemas have a valid object structure
All tool input schemas have a valid object structure
Tool names use valid characters
All tool names use valid characters
Tool names follow the MCP 1–128 character range
All tool names follow the MCP recommended length
Tool names follow MCP uniqueness guidance
All tool names are unique
Tool text has no hidden control characters
No invisible or control characters found in tool-facing text
Tool-linked resource URI is readable
All tool-linked resource URIs are readable
Tool invocation metadata present
All view-linked tools have invoking/invoked metadata
Tool visibility metadata is valid
All explicit ui.visibility arrays are valid
MCP Apps
All discovered view resources were inspected
Inspected all 3 discovered view resource(s)
View resource envelope is valid
All view resources are readable and use ui:// with a supported MCP Apps HTML MIME type
View resource metadata complete
3 resource(s) have incomplete metadata
How to fix: Use a ui:// URI and text/html;profile=mcp-app. For mcp-use servers, set the widget description in widgetMetadata; other stacks can use _meta.ui.widgetDescription or the OpenAI compatibility alias.
CSP metadata covers literal external origins
All statically detectable external origins are declared in CSP metadata
View resources declare a domain
3 ChatGPT UI domain issue(s) found
How to fix: For ChatGPT submission, set one exact HTTPS origin such as "https://app.example.com" on every view via _meta.ui.domain (or openai/widgetDomain). Paths are not valid and all views in one app must share the origin.
Declared domains respond
All declared domains are reachable
Client compatibility
Claude Code metadata fits its 2 KB fields
Tool descriptions and server instructions fit Claude Code's 2 KB fields
Skills over MCP resources are readable
Server does not advertise the Skills over MCP extension
Claude tools declare applicable behavior hints
All tools include an applicable readOnlyHint or destructiveHint
All tools have a display title
All tools have a display title
ChatGPT tool names are unique
All tool names are unique
Claude tool names are within 64 characters
All tool names are within Claude's 64-character limit
Cursor tool-name budget advisory
No tool name independently exhausts Cursor's observed 60-character combined budget
OpenAI file parameters use valid schemas
All declared OpenAI file parameters use reviewer-valid schemas
Overview
- Author
- Backstage, LLC
- Verification
- community
- Auth
- None — public endpoint
- Categories
- creativemedia-entertainment
- Works with
- claudeclaude-apiclaude-codeclaude-desktop
- Docs
- Documentation
get_casting_call_detailsget_similar_casting_callssearch_casting_callsRelated MCP servers
FAQ
Backstage install, tools, readiness, and alternatives.
How do I add Backstage to Claude, ChatGPT, or Cursor?
Add Backstage to Claude, ChatGPT, or Cursor by connecting its remote MCP URL in each client's MCP settings. In Claude, add a custom connector. In ChatGPT, add an MCP app. In Cursor, add an MCP server under Settings. The MCP URL is https://mcp.backstage.com/mcp.
Is Backstage MCP ready for ChatGPT and Claude?
As of September 15, 2026, Backstage scores 93/100 on Manufact's MCP publishing checklist. The scan does not yet meet ChatGPT publishing checks and meets Claude publishing checks.
What tools does the Backstage MCP server provide?
Backstage provides these MCP tools: get_casting_call_details, get_similar_casting_calls, and search_casting_calls.
What are the best alternatives to Backstage?
As of September 15, 2026, alternatives to Backstage in creative on the Manufact MCP catalog include AI Video Prompt Generator: Vivideo.ai, Autodesk Product Help, Epicure, Clipkit, and Alpix.
Does Backstage MCP require authentication?
Backstage does not require authentication. It is a public MCP endpoint you can connect without logging in.
Who develops Backstage?
Backstage is developed by Backstage, LLC. It is listed as community on the Claude connector directory.
Not your MCP?
Scan any public or OAuth MCP URL against ChatGPT and Claude publishing checks. No account required.