Venue MCP Endpoint

Venue.sh exposes a built-in MCP (Model Context Protocol) endpoint so you can use your organization's catalog, documentation, templates, and plugin data from AI tools that support MCP. Using the endpoint is as simple as adding it to your AI tool's settings and signing in with your Venue.sh account.

Two MCP features

This page covers Venue.sh's built-in MCP endpoint - the URL your IDE or desktop app connects to for OAuth access to Venue data.

To register and browse MCP servers your organization uses (e.g., Atlassian, Context7, or internal services), see MCP Servers.

The endpoint provides the same capabilities that are available in the Venue.sh Assistant:

Software catalog - Search and fetch entities (APIs, Components, Groups, Locations, Rules, Templates, Users)
Technical documentation - Search and read TechDocs
Templates - Get template schemas and validate YAML for scaffolding
Plugin integrations - Data from enabled plugins (Jira, GitHub, GitLab, PagerDuty, Snyk, Confluence, and the other supported plugins)

Alongside these tools, the endpoint publishes resources and prompts so your AI tool can discover what is available on its own. See Resources and Prompts below.

How It Works

First, you add the Venue.sh MCP endpoint in your AI tool (Cursor or Claude Desktop), using your Venue.sh dashboard URL.
Once the tool connects, you sign in with your Venue.sh account (OAuth in the browser).
After that, the tool can use your organization's data to answer questions. You stay in your IDE or desktop app with full context.

Your Venue administrator does not need to enable anything extra for MCP. If you can use the Assistant in the Venue.sh portal, you can use the same data via MCP once the server is connected and you're signed in.

Connecting to the Venue MCP Endpoint

The exact steps depend on your AI tool. Look for options like "Add MCP server," "Remote server," or "OAuth" and use your Venue.sh dashboard base URL plus /mcp. If your tool asks for OAuth metadata, it can discover it from your Venue.sh instance automatically.

Prerequisites

A Venue.sh account and access to your organization's Venue.sh instance
Your Venue.sh dashboard URL (https://dashboard.venue.sh)
An AI application that supports MCP with OAuth (e.g., Cursor, Claude Desktop)

Cursor

Open Cursor Settings > MCP (or Features > MCP).

Add the following:

{
  "venuesh": {
    "url": "https://dashboard.venue.sh/mcp"
  }
}

When Cursor connects, complete the sign-in flow in the browser with your Venue.sh account.

Claude Code

Run the following command to add the Venue.sh MCP server to Claude Code:

claude mcp add --transport http venuesh https://dashboard.venue.sh/mcp

Claude Desktop

Open Claude > Settings > Developer > Edit Config.
Add an MCP server entry that points to your Venue dashboard URL, (https://dashboard.venue.sh/mcp).
Restart Claude Desktop.
Sign in with your Venue.sh account when prompted.

tip

If your tool supports "OAuth-protected resource" or "resource metadata" URLs, the Venue MCP endpoint publishes the required metadata so the tool can complete the OAuth flow.

Resources and Prompts

Beyond tools, the Venue MCP endpoint exposes resources and prompts. Most AI tools surface these automatically once you connect, so your agent can learn what Venue.sh offers without you spelling it out.

Resources

Resources are readable data your AI tool can fetch by URI.

Resource	What it returns
`venue://guide`	A getting-started guide describing Venue.sh MCP capabilities, tool categories, and example workflows.
`venue://tools`	The full tool catalog with names, categories, descriptions, and input parameter schemas.
`venue://plugins`	The integrations currently enabled for your organization.
`venue://catalog/entities/{kind}`	A bounded list of catalog entities for a given kind, for example `venue://catalog/entities/Component`.

All resources are scoped to the organization you signed in with.

Prompts

Prompts are reusable instructions that guide an agent through a task using the right tools in the right order.

Prompt	What it does
`how-to-search-catalog`	Walks the agent through searching the catalog, then optionally fetching full entity details. Accepts an optional entity kind.
`how-to-search-code`	Walks the agent through searching ingested repository content, then summarizing what it found. Accepts a query and an optional repository.

tip

If your agent is guessing at tool names, point it at venue://guide first. The guide explains which tool to reach for and gives worked examples.

Troubleshooting

Situation	What to do
Sign-in fails or "Authentication required"	Ensure you use the same Venue dashboard URL your organization uses and that you have an active Venue account. Try signing in again in the browser.
No data or "Organization not found"	Your user must be linked to at least one organization in Venue.sh. Contact your Venue administrator if you don't have access.
Tool not connecting	Check that the URL is correct, including `https://` and `/mcp`.
Plugin data missing	Same as in the portal: Plugins must be enabled by your Venue administrator. The AI can only use data from integrations that are enabled for your instance.
Your agent picks the wrong tool	Ask it to read the `venue://guide` resource, or invoke the `how-to-search-catalog` or `how-to-search-code` prompt for step-by-step guidance.

How It Works​

Connecting to the Venue MCP Endpoint​

Cursor​

Claude Code​

Claude Desktop​

Resources and Prompts​

Resources​

Prompts​

Troubleshooting​

See Also​