Other Clients

Most MCP clients can connect to a remote server directly. In your client, find the option to add a remote or custom MCP server (it may be called a custom connector, custom app, or server), and enter this URL:

https://mcp.givebutter.com/mcp

Your client opens a browser window so you can sign in to Givebutter and approve access. You don’t need an API key or client ID. If your client asks for a transport type, choose Streamable HTTP.

JSON configuration

If your client uses a JSON configuration file, add Givebutter as a URL-based server:

{
  "mcpServers": {
    "givebutter": {
      "url": "https://mcp.givebutter.com/mcp"
    }
  }
}

Some clients name this key serverUrl or httpUrl, or expect "type": "http" alongside it. Check your client’s MCP documentation.

Clients that only support local servers

Use this only if your client can’t connect to a remote URL and only runs local (stdio) servers. The open-source mcp-remote bridge runs on your computer and forwards requests to Givebutter. It requires Node.js 18 or later.

{
  "mcpServers": {
    "givebutter": {
      "command": "npx",
      "args": ["-y", "mcp-remote@latest", "https://mcp.givebutter.com/mcp"]
    }
  }
}

If your client accepts a URL, enter the URL instead. See How connecting works for the sign-in flow and troubleshooting.

Overview

Connect an assistant

Reference

JSON configuration

Clients that only support local servers

​JSON configuration

​Clients that only support local servers

JSON configuration

Clients that only support local servers