FAQ

5
Have a Question?

What is Disco?

Disco allows people to start integrations, add needed credentials, and share them with their team. It's a centralized platform for managing AI integrations through the Model Context Protocol.

What's coming next?

We're building capabilities to remix integrations and add combinations of tools so that one server works as a person with different capabilities. For example, a solutions engineer with access to Jira, notetaker, codebase, and read access to production database.

What is "vibe coding"?

We're adding capabilities to "vibe code" new tools given some context about an external system as an OpenAPI spec or docs URL. This allows for rapid integration development based on existing documentation.

What's the status and cost?

This project is experimental and in research preview. It is also completely free to use - courtesy of StackOne.

How do I authenticate with MCP servers?

We support multiple authentication methods for your convenience:

  • Query parameter (recommended): Add ?server_key=your_server_key to the URL
  • Authorization header: Include Authorization: Bearer your_server_key in your requests
  • URL path (legacy): The original /connector/server_key/sse format is still supported for backwards compatibility

The new v1 API endpoints use the format: /v1/connector/mcp?server_key=your_key