Skip to main content

Supported MCP Clients

The Venturu MCP server uses the Streamable HTTP transport, which is supported by a growing number of AI assistants and development tools. Any client that implements the MCP specification can connect.

AI Assistants

ClientStatusNotes
Claude DesktopSupportedFull tool support with OAuth authentication
ChatGPTSupportedEnhanced experience with interactive listing and broker cards
Claude (Web)SupportedWorks via the MCP integrations panel

Development Tools

ClientStatusNotes
CursorSupportedAvailable in Agent mode
WindsurfSupportedRemote MCP server support
VS CodeSupportedVia MCP extensions
ClineSupportedRemote server configuration

Frameworks & Libraries

FrameworkTransportNotes
MCP TypeScript SDKStreamable HTTP@modelcontextprotocol/sdk
MCP Python SDKStreamable HTTPmcp package
mcp-handlerStreamable HTTPUsed to build the Venturu server itself

Client-Specific Features

ChatGPT Apps SDK Widgets

When accessed from ChatGPT, the Venturu MCP server returns interactive HTML widgets for search results. Business listings and broker profiles are rendered as rich, visual cards directly in the conversation — with images, pricing, and direct links.
Widget resources are served automatically when the server detects a ChatGPT client. No additional configuration is needed.

Voice Agent Integration

The Venturu MCP server supports integration with voice AI platforms like ElevenLabs Conversational AI. A pre-registered OAuth client allows voice agents to authenticate and use all tools, including contact tools, on behalf of users.

Building a Custom Client

If you’re building your own MCP client, connect using these details:
{
  "name": "com.venturu/mcp-server",
  "version": "1.0.0",
  "remotes": [
    {
      "type": "streamable-http",
      "url": "https://www.venturu.com/mcp"
    }
  ]
}

Discovery Endpoints

EndpointURL
OAuth Authorization Serverhttps://www.venturu.com/.well-known/oauth-authorization-server
Protected Resource Metadatahttps://www.venturu.com/.well-known/oauth-protected-resource

Authentication Flow

  1. Discover endpoints via .well-known/oauth-authorization-server
  2. Register your client via Dynamic Client Registration (/api/oauth/mcp/register)
  3. Initiate OAuth 2.0 + PKCE authorization flow
  4. Exchange authorization code for access and refresh tokens
  5. Include the access token as a Bearer token in MCP requests
See the Authentication page for full details.