Skip to main content
A custom MCP server connects your workflows to any remote MCP (Model Context Protocol) endpoint that Spojit doesn’t ship a built-in connector for. Point Spojit at a third-party hosted server, or at one your own team runs, and its tools become available to workflows just like any first-party connector. Reach for a custom server when the service you need isn’t in the catalog and the HTTP Requests connector is too low-level: a custom server gives you typed, discoverable tools plus the same Agent Mode and Direct Mode behaviour as any other connector.
The server must be a remote endpoint that speaks Streamable HTTP MCP (for example https://api.example.com/mcp). Spojit discovers the tool list live from the server, so it always reflects the server’s current state.
Many vendors host their own MCP server. Each guide below covers that vendor’s prerequisites, the exact server URL, how to sign in, and links to the vendor’s own documentation.

​
Servers with a built-in connector

These have a Spojit connector already, so you add them from the catalog with Add Connection instead of adding a custom server.

GitHub

Repos, issues, pull requests, Actions

Stripe

Payments, invoices, subscriptions

Snowflake

Cortex Analyst, Search, SQL

Intercom

Conversations, contacts, tickets

PagerDuty

Incidents, schedules, on-call

Tavily

Web search, extraction, crawling

​
Custom servers that sign in with Auto

Paste the server URL, keep Auto authentication, click Save & connect, and approve access when the vendor asks.

NetSuite

Oracle’s AI Connector Service

Atlassian

Jira, Confluence, Jira Service Management

Notion

Pages and databases

Linear

Issues and projects

monday.com

Boards and items

ClickUp

Tasks, docs, time tracking

Airtable

Bases and records

Miro

Boards

Canva

Designs, assets, exports

Webflow

CMS, pages, sites

PayPal

Invoices and transactions

Sentry

Issues and errors

Datadog

Logs, metrics, monitors

Grafana Cloud

Metrics and logs

Cloudflare

API, observability, Radar

Supabase

Projects and databases

Neon

Serverless Postgres

Hugging Face

Models, datasets, Spaces

​
Custom servers that need your own OAuth app

These vendors want you to register an app in their admin console first. Choose Auto and the sign-in form fills in the vendor’s endpoints; you add the client ID and secret.

Salesforce

Hosted MCP Servers

HubSpot

CRM and marketing

Dynamics 365 (Dataverse)

Tables and records

Slack

Search, channels, messages

Asana

Tasks and projects

Box

Files, folders, Box AI

Zoom

Meetings and recordings

​
Don’t see your server?

Any vendor that publishes a remote MCP server over Streamable HTTP should work. Follow the steps below: try Auto first, use Token if the vendor only accepts a key, and OAuth 2.0 if it needs an app you register yourself.

​
Add a custom server

1

Open the Connections page

Go to Connections and click Add custom server (next to Add Connection).
2

Enter the basics

  • Name: a label to identify this server, for example Internal CRM MCP.
  • Server URL: the full MCP endpoint, for example https://api.example.com/mcp.
  • Icon URL (optional): an https:// image URL to show as the connection’s icon.
3

Choose an authentication mode

Auto is selected by default; switch to None, Token, or OAuth 2.0 if the server requires it. See Authentication modes below.
4

Set visibility and save

Choose Organization (all members can see and use it) or Private (only you and admins). Click Save. The server appears under My Connections.

​
Authentication modes

Custom servers support four modes. Check the server’s own documentation for which one it expects.

​
Auto (default)

Most hosted MCP servers follow the MCP authorization standard: the server tells clients where its login service is, and clients register themselves with it. Spojit does this for you.
1

Choose Auto and save

Click Save & connect. Spojit asks the server how to sign in, registers itself with the server’s login service, and sends you to that service to approve access.
2

Approve access

The consent page names Spojit as the application asking for access. After you approve, Spojit stores the tokens and marks the connection Connected. Access tokens refresh automatically.
Spojit identifies itself to the login service as a public client with PKCE, using a client metadata document it hosts at https://miraxa.spojit.com/oauth/client-metadata.json. Nothing about your organisation is included in that document.
If the server’s login service accepts neither of the two automatic registration methods, the dialog switches to the OAuth 2.0 form with the discovered endpoints already filled in, and you complete it with an app you register yourself (see below). The server is saved either way; use Reconnect on the connection to re-run discovery later, for example after the server changes its login service.

​
None

For public servers, or servers that authenticate at the network boundary (VPN, mutual TLS). Some servers accept a key directly in the URL query string, in which case no separate credential is needed.

​
Token (header)

Spojit sends a token on a header with every request. In the dialog, choose Token and set:
  • Token: the secret value, stored securely (never shown again after saving).
  • Header name: default Authorization.
  • Prefix: default Bearer.
The default sends Authorization: Bearer <token>. For an API-key header such as X-API-Key, set the header name and clear the prefix. Click Add to save.

​
OAuth 2.0 (bring your own app)

For servers backed by a standard OAuth provider that does not support automatic registration, or when you prefer to use an OAuth app you control. You supply your own OAuth app’s details:
1

Register the redirect URI on your OAuth app

Add this callback URL to your provider’s OAuth app:
2

Fill in the OAuth fields

Choose OAuth 2.0 and enter the Authorization URL, Token URL, Client ID, Client Secret, and Scopes. Under Advanced you can toggle PKCE and switch client authentication between POST body and Basic header.
3

Save and authorize

Click Save. Spojit redirects you to the provider to consent, then stores the tokens and marks the connection Connected. Access tokens refresh automatically.
Changing scopes (or the OAuth app) after connecting does not re-issue the token. Save your changes, then use Reconnect on the connection to re-authorize with the new scopes.

​
Use a custom server in a workflow

Once the connection exists, add it to a workflow:
1

Add a Connector node

Drag a Connector node onto the canvas and open Select Connector.
2

Pick it under Custom Servers

Custom servers appear in their own Custom Servers section at the top of the picker. Select yours.
3

Choose tools and mode

Spojit discovers the server’s tools live. Use Agent Mode to let the AI choose tools, or Direct Mode to call a specific tool. Optionally narrow the tool list under Available Tools.

​
Edit or reconnect

Use the Configure button on the connection to change the name, URL, icon, or auth. For a token connection, leave the token blank to keep the current one; for OAuth, leave the client secret blank to keep it, or enter a new one to rotate it. Use Reconnect to re-run the OAuth flow after changing scopes or credentials.

​
Caveats

  • Reachable from Spojit: the server URL must be reachable from Spojit’s runtime, not just your machine. Internal-only servers need a VPN or reverse proxy.
  • Secrets are stored securely: tokens, client secrets, and OAuth tokens are stored securely and never shown after saving.
  • You own the OAuth app: for OAuth 2.0 mode you create and manage the OAuth application; Spojit only stores the credentials you supply. In Auto mode Spojit is the registered application and no credentials of yours are involved.
  • Icons are https only: the optional Icon URL must be an https:// image URL.
  • Tenant-scoped: a custom server is visible only within your organization. Its visibility (Organization or Private) controls who inside the tenant can see and use it.

​
Troubleshooting

Confirm the URL is correct and reachable from Spojit’s runtime. Check that the server is running and responding on the Streamable HTTP MCP endpoint.
The message says what was found. “Answered without requiring authorization” means the server is open: choose None. “Publishes no protected resource metadata” means the server does not follow the MCP authorization standard: use Token or OAuth 2.0 as its documentation describes. “Client registration was rejected” quotes the login service’s own reason; the OAuth 2.0 form opens prefilled so you can continue with an app you register yourself.
Verify the token is current and the header name matches what the server expects (for example Authorization versus X-API-Key). For OAuth, confirm the redirect URI is registered with the provider and the scopes are correct.
Confirm the endpoint is an MCP server that returns a tool list. Re-saving the connection re-runs tool discovery, so new tools on the server become available without recreating the connection.