MCP Servers

MCP Servers in Venue.sh let your organization register, discover, and inspect Model Context Protocol (MCP) servers in one place. Platform teams get a shared registry of available AI tools, and developers can browse what each server exposes before wiring it into an IDE or agent workflow.

The MCP Server catalog is separate from Venue's built-in MCP endpoint, which lets external AI tools query your Venue.sh data. The catalog is for documenting any MCP server your organization uses - internal services, vendor integrations, or local development servers.

Key Capabilities

• Registration - Register MCP servers by URL (auto-extract capabilities) or by manual entry.
• Discovery - Browse and search registered servers across your organization.
• Inspection - View the tools, resources, and prompts exposed by each server.
• Refresh - Re-extract capabilities for URL-registered servers when they change.
• Assistant integration - Ask the Assistant about registered servers using natural language.

Registered MCP servers are also synced to the software catalog as MCPServer entities, so you can relate them to Components and other catalog entities.

Browsing MCP Servers

1. Open MCP Servers from the sidebar (under AI).
2. Use the search box to filter by name or description.
3. Click a server to open its detail page.

Each list row shows the server name, description, transport type, status, and counts for tools, resources, and prompts.

Registering an MCP Server

You need create permission on MCP Servers to register a new server. Contributors and viewers can browse servers but cannot add or edit them.

URL-based registration (recommended)

URL-based registration connects to the MCP server, performs the protocol handshake, and automatically extracts its tools, resources, and prompts.

1. Go to MCP Servers and click Add MCP Server.
2. Enter a name and optional description.
3. Enter the server URL (e.g., https://mcp.example.com/mcp).
4. If the server requires authentication, choose a credential type and provide the values:
   • Bearer token
   • API key (with optional custom header name)
   • Basic auth (username and password)
   • Custom header (name and value)
5. Submit the form. Venue.sh connects to the server and populates its capabilities.

Credentials are stored securely. They are never shown in the UI or returned by API responses after registration.

Manual registration

Use manual registration when the server is not reachable from Venue.sh, or when you want to document capabilities without a live connection.

1. Go to MCP Servers and click Add MCP Server.
2. Switch to manual registration mode.
3. Enter server metadata (name, description, transport type).
4. Add tools, resources, and prompts via the form.

Manual servers do not support on-demand capability refresh. Update them by editing the record.

Viewing MCP Server Details

The detail page shows:

• Metadata - Name, description, URL, transport, status, and whether credentials are configured.
• Tools - Name, description, and input schema where available.
• Resources - URI patterns, names, MIME types, and descriptions.
• Prompts - Name, description, and argument lists.

For URL-registered servers, click Refresh Capabilities to re-connect and update the stored tools, resources, and prompts. If the server is unreachable during refresh, the previous capabilities are retained and an error is shown.

Useful Things to Ask About

The Assistant can answer questions about your registered MCP servers. For example:

• "Which MCP servers are registered in our organization?"
• "What tools does the Atlassian MCP server expose?"
• "List all MCP servers with more than 10 tools."

The Assistant uses the same catalog data shown on the MCP Servers pages.

Permissions

MCP Server access follows the same pattern as repository content:

Role	Permissions
Admin, Editor	Create, Read, Update, and Delete
Contributor, Viewer, Demo	Read only

Registration, updates, and deletions are recorded in the Activity Log.

Troubleshooting

Situation	What to do
Registration fails with a connection error	Verify the URL is correct and the server is reachable from Venue.sh. Check that credentials are valid if required.
Server registered with empty capabilities	The server may have connected but reported no tools, resources, or prompts. Confirm the server is fully configured on the provider side.
Refresh fails	The server may be down or credentials may have expired. The previously stored capabilities are kept until a successful refresh.
Duplicate server error	A server with the same URL is already registered in your organization. Edit the existing record instead.
Cannot see the Add button	Your role may not include MCP Server create permission. Contact your Venue administrator.

See Also

• Venue MCP Endpoint - Connect external AI tools (Cursor, Claude Desktop) to query Venue.sh data.
• Skills - Browse agent skills auto-discovered from connected repositories.
• Assistant - Using the Assistant in the Venue.sh portal.