Provider REST API

19 actions

Connect Claude to GitHub

Manage repositories, issues, pull requests, and Actions. Toolspoke puts 19 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connect View pricing

Connection: Provider REST API
Authentication: Personal access token
Actions exposed: 19
Cost per call (typical): 1 credit
Adapter: Maintained by Toolspoke

Connected in three steps

1
Install GitHub
Open the marketplace in your workspace, add GitHub to the project your agents work in, and it appears on the gateway immediately.
2
Connect the credential
Authenticate with personal access token. Where to get one, and what it has to be able to reach, is the next section.
3
Point your agent at the gateway
Give your client one address, https://toolspoke.com/mcp. Claude Code takes it as a command, Claude and Claude Desktop add it as a custom connector, and Cursor, Codex and VS Code each read it from a config file of their own.

.mcp.json

{
  "mcpServers": {
    "toolspoke": {
      "type": "http",
      "url": "https://toolspoke.com/mcp"
    }
  }
}

One block covers every tool you have installed. GitHub shows up in the client as soon as your policy allows it, and so does everything else you install later.

Where the address goes, per client

Claude Code: Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcp
Claude and Claude Desktop: Settings, then Connectors, then Add custom connector
https://toolspoke.com/mcp
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json for one project
{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }
Codex: ~/.codex/config.toml
[mcp_servers.toolspoke] url = "https://toolspoke.com/mcp"
VS Code: .vscode/mcp.json, or the MCP: Add Server command
{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }

What GitHub asks for

Personal access token. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

Personal access tokenRequired: Settings → Developer settings → Personal access tokens. Fine-grained tokens need Contents, Issues, Pull requests, and Actions read/write on the repositories you want to reach.; github_pat_… or ghp_…
Enterprise Server URLOptional: Only for GitHub Enterprise Server. Leave blank for github.com.; https://github.example.com

What Claude can do in GitHub

19 actions, each one declared and named by the connector rather than discovered at runtime. A workspace policy grants a person all of them, a hand-picked selection, everything on the read side, everything on the write side, or none.

Reads: 14Reads
Writes: 5Writes
Destructive: 0Destructive

Reads

Fetches data and changes nothing.

list_my_repos
List repositories, newest activity first. Omit owner to list the repositories the token's own account can reach (including private and organisation ones); pass owner to list a specific organisation's or user's repositories. Use this to resolve a repository's exact owner/repo pair and default branch before other actions.
list_org_repos
List an organisation's repositories. Use list_user_repos for a personal account, and list_my_repos for the authenticated account's own repositories.
list_user_repos
List a user's public repositories. Use list_org_repos for an organisation, and list_my_repos for the authenticated account's own repositories.
search_repositories
Search public and accessible repositories with GitHub search syntax, e.g. "language:go stars:>500 topic:cli" or "org:vercel next". Use this to find a repository when you do not already know its owner/repo pair.
list_issues
List issues in a repository, newest updated first by default. Pull requests are excluded - use list_pull_requests for those. Filter by state, labels, assignee, or an updated-since timestamp to keep the result small.
get_issue
Fetch one issue with its full body. Set include_comments to also pull the discussion thread. Works for a pull request number too, but returns only its issue-side fields - use get_pull_request for branch and diff detail.
list_issue_comments
Read the comments on an issue, oldest first. Call get_issue first for the issue itself.
list_pull_requests
List pull requests in a repository. Filter by state, or by head ("owner:branch") and base branch to find the PR for a specific branch.
get_pull_request
Fetch one pull request with its body, merge state, and diff totals. Set include_files to also list the changed files with per-file line counts (file names and counts only, not the patch text).
list_pull_request_files
List the files a pull request changes, with per-file additions and deletions. Call get_pull_request first for the pull request itself.
get_file_contents
Read a file or list a directory from a repository at a branch, tag, or commit. Text files come back decoded and truncated at 40,000 characters; directories come back as an entry listing. Use this before quoting or editing repository content.
list_commits
List commits on a branch, optionally narrowed to one file path, one author, or a date range. Returns short SHAs and first-line messages, so pair it with get_file_contents when you need the actual change.
list_workflow_runs
List GitHub Actions runs for a repository, newest first. Narrow to one workflow file, a branch, or a status such as "failure" to check whether CI is green before merging.
list_runs_for_workflow
List runs of one workflow, newest first. Use list_workflow_runs for every workflow in the repository.

Writes

Creates or updates something on the other side.

create_issue
Open a new issue in a repository. Returns the created issue including its number and URL.
update_issue
Edit an existing issue: change its title or body, close or reopen it, or replace its labels and assignees. Pass at least one field to change; labels and assignees replace the current set rather than adding to it. Closing an issue is reversible - set state to "open" to undo it.
comment_on_issue
Post a comment on an issue or on a pull request's conversation tab. Pull requests accept the same issue number here.
create_pull_request
Open a pull request from an existing branch. The head branch must already exist and differ from base. Use draft when the work is not ready for review.
run_workflow
Trigger a workflow_dispatch run of a GitHub Actions workflow on a branch or tag. The workflow must declare a workflow_dispatch trigger, and any inputs it declares as required must be supplied. Poll list_workflow_runs afterwards for the outcome.

What it will not do

Enforced by the gateway rather than left to convention, which is why each of these can be stated flatly.

It cannot call anything else: The 19 actions above are the whole of it. A call to any other name is refused before it reaches GitHub rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time.
Nothing here deletes: This connector writes to GitHub, but nothing in it deletes or permanently alters anything.
It reaches no further than your credential: Toolspoke holds no access to GitHub of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either.
It never hears from GitHub: Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in GitHub. An agent has to ask.
It does not smooth over provider limits: Toolspoke does not retry, queue or back off around GitHub's own rate limits. A call that GitHub refuses comes back to the agent as a failed call.

Before you connect it

What can Claude do in GitHub?

19 named actions: 14 that only read and 5 that write. They include list_my_repos, list_org_repos and list_user_repos. Nothing outside that list is reachable: the connector declares each operation by name rather than proxying whatever an agent asks for.

What credentials does the GitHub connector need?

Personal access token. The connector asks for personal access token, and optionally enterprise server url. Values are encrypted at rest and attached to the outbound request by the gateway, so they are never part of the arguments an agent sends and never reach the audit log.

Does the GitHub connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 19 actions. There is a single address, https://toolspoke.com/mcp. Claude Code adds it with claude mcp add --transport http, Claude and Claude Desktop take it as a custom connector in settings, Cursor reads it from .cursor/mcp.json, Codex from ~/.codex/config.toml, and VS Code from .vscode/mcp.json. Each of them signs in to the gateway itself, so there is no key to paste.

What does the GitHub connector not do?

The 19 actions above are the whole of it. A call to any other name is refused before it reaches GitHub rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time. This connector writes to GitHub, but nothing in it deletes or permanently alters anything. Toolspoke holds no access to GitHub of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either. Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in GitHub. An agent has to ask. Toolspoke does not retry, queue or back off around GitHub's own rate limits. A call that GitHub refuses comes back to the agent as a failed call.

Can I limit which actions an agent can call?

Yes, in two places. The project switches GitHub's actions on and off one at a time, for everyone in the project at once, and the screen groups them by read, write and destructive so turning off everything that deletes is one click. An individual agent key can then be narrowed further, to particular toolkits in a project and to particular actions in a toolkit. Whatever it was granted, a key never reaches a project its owner cannot.

What gets recorded when an agent calls GitHub?

Every attempt, with the agent that made it and the person that agent belongs to, the full request payload, the response payload, the status, the duration, and the credits spent. Values whose key names a secret are masked out before the record is shown to anyone. An operation the connector marks as not retained never has its response body written at all, so the gateway keeps no second copy of what was read.

More developer tools connectors

Browse all of them