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/mcpThe 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 GitDailies install. To connect a specific install, or to connect several side by side, use its own endpoint:
https://mcp.gitdailies.com/install/<install-id>/mcp
The install ID is the number in your browser’s address bar when you open that 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
- Open Settings → Connectors.
- Click Add custom connector.
- Enter the name
GitDailiesand the server URLhttps://mcp.gitdailies.com/mcp. - 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/mcpThen, 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
Custom MCP connectors are available in ChatGPT’s developer mode, on plans that support it.
- Open Settings → Apps & Connectors → Advanced settings, and turn on Developer mode.
- Back in Apps & Connectors, click Create.
- Enter the name
GitDailiesand the server URL, choose OAuth authentication, and click Create. - Sign in to GitDailies when prompted.
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.
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 getConnectionInfo 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 the Max plan. Ask your assistant to run getConnectionInfo: if
mcpAccessIncluded is false, an organization admin can upgrade from the Settings page of the
GitDailies web app.
The agent is looking at the wrong organization. Each connection is bound to one install. Remove the connection and add it again with that install’s own endpoint (see Server URL above).
A repo is missing from the results. The server only reports on repos that your install follows in GitDailies.
“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.