Custom MCP Server
Register any Model Context Protocol server with a URL. Orqestr discovers tools, resources, and prompts over Streamable HTTP, executes them from agent runs with clear namespacing, and honors per-agent permissions plus optional human approval before sensitive calls.
What your agents can do with Custom MCP Server
- Discover tools, resources, and prompts from any compatible MCP endpoint
- Call MCP tools during agent runs with timeouts and isolated error handling
- Namespace capabilities per connection so tool names stay readable in prompts
- Refresh OAuth tokens automatically and prompt to reconnect when refresh fails
- Mix MCP tools with built-in agent tools and thousands of other integrations
How you can authenticate
Orqestr picks bearer auth or standard OAuth 2.0 from your server URL. You can use different methods on different MCP connections.
Bearer token or API key
Paste a static secret when the server expects a fixed Authorization header or API key. Orqestr encrypts credentials at rest and attaches them to each MCP request.
Standard OAuth 2.0
When the server implements OAuth 2.0 the way MCP expects (protected resource and authorization server metadata at `.well-known`, PKCE, and dynamic client registration where applicable), Orqestr opens the provider consent screen in your browser, stores tokens encrypted, and refreshes access tokens so the connection keeps working.
Use cases
Internal APIs and microservices
Expose an internal HTTP API or microservice as MCP so agents can query systems that do not have a first-party Pipedream app, without opening broad network access.
Hosted vendor MCP
Connect to SaaS-hosted MCP endpoints the same way you add a custom URL: one flow for discovery, auth, and agent access across vendors.
Developer and data workflows
Let agents run linters, fetch docs, trigger CI jobs, or read observability data through MCP servers your team already operates.
How it works
Add your server
Open Integrations in a project, choose Add MCP Server, and enter a display name plus the server base URL. Orqestr connects and pulls the capability list.
Authenticate
Complete standard OAuth 2.0 in the browser when the server advertises it, or paste a bearer token when it does not. Custom URLs are probed so the OAuth path appears automatically when the server follows the expected discovery pattern.
Configure agents
Grant specific agents access to the connection, tune allow, ask approval, or disabled per tool, then run tasks as usual.
Related integrations
Ready to connect Custom MCP Server to your AI agent team?
Start with the free plan. No credit card required. Connect Custom MCP Server and 3,000+ other tools.