Skip to content

Connect your AI assistant to GitDailies

The GitDailies MCP Server is a hosted, remote MCP server. There is nothing to install or run locally. Add its URL to your AI client, sign in, and you’re ready to go.

Server URL

https://mcp.gitdailies.com/mcp

The server uses the Streamable HTTP transport and OAuth sign-in. When you first connect, your client opens a browser window where you sign in to GitDailies and approve access.

More than one organization? Each connection is bound to a single organization. To connect a specific organization, or to connect several side by side, use its own endpoint:

https://mcp.gitdailies.com/install/<install-id>/mcp

<install-id> is the ID of the GitDailies install for that organization: the number in your browser’s address bar when you open the organization in the GitDailies web app (app.gitdailies.com/install/<install-id>). Give each connection a distinct name, such as gitdailies-acme, so you and your agent can tell them apart.

Claude

Claude.ai and Claude Desktop

  1. Open Settings → Connectors.
  2. Click Add custom connector.
  3. Enter the name GitDailies and the server URL https://mcp.gitdailies.com/mcp.
  4. Click Add, then Connect, and sign in to GitDailies when prompted.

On Team and Enterprise plans, an owner may need to add the connector for the organization first.

Claude Code

Add the server from your terminal:

claude mcp add --transport http gitdailies https://mcp.gitdailies.com/mcp

Then, in a Claude Code session, run /mcp, select gitdailies, and choose Authenticate to sign in.

Add --scope user to make the server available in all of your projects, or --scope project to share it with your team through the repo’s .mcp.json.

ChatGPT

You add custom MCP servers in ChatGPT on the web, on plans that support them. In a Business, Enterprise, or Edu workspace, your admin’s settings decide whether you can add them.

  1. Open ChatGPT Plugins, click +, and choose Add custom MCP server.
  2. Enter the name GitDailies, and enter the server URL as the Server URL.
  3. Choose OAuth authentication.
  4. Read the warning, select I understand and want to continue, and click Create as a plugin.
  5. Install the plugin, and sign in to GitDailies when prompted.

To use it, type @ in a new chat and select GitDailies.

Cursor

Add the server to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

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

Open Cursor Settings → MCP, and click Connect next to gitdailies to sign in.

VS Code (GitHub Copilot)

Add the server to .vscode/mcp.json in your workspace, or run MCP: Add Server from the Command Palette:

{
  "servers": {
    "gitdailies": {
      "type": "http",
      "url": "https://mcp.gitdailies.com/mcp"
    }
  }
}

Click Start above the server entry, and sign in when VS Code asks. The GitDailies tools then appear in Copilot Chat’s Agent mode.

OpenCode

OpenCode v2 or later is required.

Add the server to ~/.config/opencode/opencode.json (all projects) or opencode.json in your project root (one project):

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "gitdailies": {
      "type": "remote",
      "url": "https://mcp.gitdailies.com/mcp"
    }
  }
}

Then sign in from your terminal:

opencode mcp auth gitdailies

Run opencode mcp list to check that gitdailies shows as connected.

Other MCP clients

Any client that supports remote MCP servers over Streamable HTTP with OAuth can connect. Point it at the server URL above.

For clients that only support local (stdio) servers, you can bridge to the remote server with mcp-remote:

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

Check that it works

Ask your assistant:

Which GitDailies organization are you connected to?

It calls the get_connection_info tool and replies with your organization’s name, its plan, and whether MCP access is included. Then try a real question, such as “What PRs are waiting for my review?”

Troubleshooting

The tools return an error about MCP access. MCP access is included in every paid plan. Ask your assistant to run get_connection_info: if mcpAccessIncluded is false, your organization is on the legacy free Community plan, which doesn’t include MCP. An organization admin can move to a paid plan from the Settings page of the GitDailies web app.

The agent is looking at the wrong organization. Each connection is bound to one organization. Remove the connection and add it again with the right organization’s own endpoint (see Server URL above).

A repo is missing from the results. The server only reports on repos that your organization follows in GitDailies and your user account can access on GitHub.

“My” tools return nothing. Personal tools describe the GitHub user who authorized the connection. Check that you signed in as yourself, and that your PRs and reviews are in followed repos.

Still stuck? Contact us at support@gitdailies.com.