Skip to main content

MCP Server

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

The MCP server 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 data - Data from enabled plugins (Jira, GitHub, GitLab, PagerDuty, Snyk, Confluence, and the other supported plugins)

How It Works​

  • First, you add the Venue.sh MCP server 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.sh 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.

Adding the Venue.sh MCP Server​

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​

  1. Open Cursor Settings → MCP (or Features → MCP).
  2. Add the following: 
    {
      "venuesh": {
        "url": "https://dashboard.venue.sh/mcp"
      }
    }
  3. When Cursor connects, complete the sign-in flow in the browser with your Venue.sh account.

Claude Desktop​

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

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

Troubleshooting​

SituationWhat 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.sh administrator if you don't have access.
Tool not connectingCheck that the URL is correct, including https:// and /mcp.
Plugin data missingSame as in the portal: Plugins must be enabled by your administrator. The AI can only use data from integrations that are enabled for your instance.

See Also​