violet
Violet Labs operates an official hosted (remote) Model Context Protocol server that gives agents secure access to a workspace's structured Violet data — to answer questions, build insights, and assemble dashboards. Two environments are published: the standard cloud server and a VioletGov server for ITAR/regulated tenants. Authentication is via OAuth (recommended: authenticate with existing Violet credentials and select a workspace) or an API key passed in the X-API-Key header (for clients like Cursor and Windsurf). The OAuth flow is backed by the app.violetlabs.com authorization server (PKCE S256, dynamic client registration, scope: mcp) — see well-known/violetlabs-oauth-authorization-server.json.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Endpoint
Hosted endpoint · transport http
Connect
This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):
For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:
If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.