Setup guide

Add Dibsline to any MCP client

Dibsline is two remote MCP servers. Any client that speaks MCP over Streamable HTTP and can sign in with OAuth can use them: the assistants with their own guide, and tools such as Notion, Zapier, Make, n8n, Claude Code and Cursor.

This page says what Dibsline's own servers need. For an assistant's own steps, see its guide: Claude, ChatGPT, Gemini, Grok, Perplexity, Mistral.

What a client needs

  • Transport: Streamable HTTP (JSON responses). The server sends no streams and keeps no sessions.
  • Sign-in: OAuth 2.0 with PKCE. The client registers itself with Dynamic Client Registration, or presents a Client ID Metadata Document; no API key, and nothing to type but your email address and the code.
  • Discovery: an unauthenticated request gets 401 with the protected resource metadata (RFC 9728), so a client finds the sign-in by itself.
  • Scopes: dibsline, and offline_access for a refresh token so you are not asked to sign in every session.
  • One account works for both servers, and the Free plan covers one of them: the first you use.

The two addresses

Dibsline Permits

https://mcp.dibsline.com/permits/mcp

Dibsline Carriers

https://mcp.dibsline.com/carriers/mcp

The sign-in, step by step

  1. Give your client one of the addresses above. It discovers the sign-in and opens Dibsline's sign-in page in your browser.
  2. Type your email address. Dibsline emails you a 6-digit code; it works for 10 minutes.
  3. Type the code and allow access. The page names the client and where access is sent, so you can check it is yours.
  4. Back in your client, ask in plain English, for example "Any new pool permits in Austin this week?"

There is no password to make or to lose. A client that cannot open a browser for the sign-in cannot use Dibsline.

More

What each connector does, every tool and 7 worked examples: Permits docs, Carriers docs.

Stuck? support@dibsline.com