@sandboxapis/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SANDBOXAPIS_API_KEY | No | Lifts the anonymous limit (60 req/hr) to 600. Free key at sandboxapis.dev. | |
| SANDBOXAPIS_BASE_URL_ADO | No | Point the Azure DevOps surface elsewhere — a pinned snapshot host, or a self-hosted instance. | |
| SANDBOXAPIS_BASE_URL_JIRA | No | Point the Jira surface elsewhere — a pinned snapshot host, or a self-hosted instance. | |
| SANDBOXAPIS_BASE_URL_DEVIN | No | Point the Devin surface elsewhere — a pinned snapshot host, or a self-hosted instance. | |
| SANDBOXAPIS_BASE_URL_SLACK | No | Point the Slack surface elsewhere — a pinned snapshot host, or a self-hosted instance. | |
| SANDBOXAPIS_BASE_URL_TEAMS | No | Point the Microsoft Teams surface elsewhere — a pinned snapshot host, or a self-hosted instance. | |
| SANDBOXAPIS_BASE_URL_CURSOR | No | Point the Cursor surface elsewhere — a pinned snapshot host, or a self-hosted instance. | |
| SANDBOXAPIS_BASE_URL_GITHUB | No | Point the GitHub surface elsewhere — a pinned snapshot host, or a self-hosted instance. | |
| SANDBOXAPIS_BASE_URL_GITLAB | No | Point the GitLab surface elsewhere — a pinned snapshot host, or a self-hosted instance. | |
| SANDBOXAPIS_BASE_URL_LINEAR | No | Point the Linear surface elsewhere — a pinned snapshot host, or a self-hosted instance. | |
| SANDBOXAPIS_BASE_URL_OPENAI | No | Point the OpenAI surface elsewhere — a pinned snapshot host, or a self-hosted instance. | |
| SANDBOXAPIS_BASE_URL_SENTRY | No | Point the Sentry surface elsewhere — a pinned snapshot host, or a self-hosted instance. | |
| SANDBOXAPIS_BASE_URL_CHATGPT | No | Point the ChatGPT surface elsewhere — a pinned snapshot host, or a self-hosted instance. | |
| SANDBOXAPIS_BASE_URL_HUBSPOT | No | Point the HubSpot surface elsewhere — a pinned snapshot host, or a self-hosted instance. | |
| SANDBOXAPIS_BASE_URL_ZENDESK | No | Point the Zendesk surface elsewhere — a pinned snapshot host, or a self-hosted instance. | |
| SANDBOXAPIS_BASE_URL_CIRCLECI | No | Point the CircleCI surface elsewhere — a pinned snapshot host, or a self-hosted instance. | |
| SANDBOXAPIS_BASE_URL_ANTHROPIC | No | Point the Anthropic surface elsewhere — a pinned snapshot host, or a self-hosted instance. | |
| SANDBOXAPIS_BASE_URL_BITBUCKET | No | Point the Bitbucket surface elsewhere — a pinned snapshot host, or a self-hosted instance. | |
| SANDBOXAPIS_BASE_URL_BUILDKITE | No | Point the Buildkite surface elsewhere — a pinned snapshot host, or a self-hosted instance. | |
| SANDBOXAPIS_BASE_URL_PAGERDUTY | No | Point the PagerDuty surface elsewhere — a pinned snapshot host, or a self-hosted instance. | |
| SANDBOXAPIS_BASE_URL_SALESFORCE | No | Point the Salesforce surface elsewhere — a pinned snapshot host, or a self-hosted instance. | |
| SANDBOXAPIS_BASE_URL_STATUSPAGE | No | Point the Statuspage surface elsewhere — a pinned snapshot host, or a self-hosted instance. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| orientA | START HERE. Returns everything needed to use SandboxAPIs with no docs: the universe/theme, every API surface and its base URL (git hosts and issue trackers), live-vs-snapshot modes and how to pin, the org and its teams/repos, notable entry points (each with a ready-to-run REST path), where the coverage manifest lives, and this server's access block — whether a key is set and how many requests are left this hour. Writes: this server is READ-ONLY, including for a scratch-enabled key — the scratch layer (a per-key, 24-hour overlay: GitHub issues and issue comments, Jira comments and transitions, and Slack messages into existing channels) is a REST feature, so use the GitHub, Jira or Slack base URL above with your key for it, and expect the tools here to answer from the shared data set alone. |
| check_budgetA | Costs nothing — call it before any loop of more than a handful of requests. Returns this server's real hourly window (limit, remaining, when it resets) read from the provider's own budget endpoint, which is exempt from the budget it reports, plus whether a key is set and where to raise the limit. The window is ONE bucket per caller shared across every provider host, so the numbers apply to all of them. |
| list_repositoriesB | List repositories for the universe's org. Results are identical to the provider's REST API and carry provider-form ids (node_id / numeric id). |
| get_repositoryC | Fetch one repository by name (default: the flagship repo). Provider-shaped, with provider-form ids. |
| list_pull_requestsC | List a repo's pull requests (GitHub) or merge requests (GitLab). Optional state filter. |
| get_pull_requestB | Fetch one PR (GitHub) / MR (GitLab) plus its reviews (GitHub) / approvals (GitLab). Returns both in one result; each carries provider-form ids for cross-referencing. |
| list_issuesC | List a repo's issues. Optional state filter (open/closed/all). |
| get_userC | Fetch a user by login/username. Provider-shaped, with provider-form ids. |
| search_commits_by_authorB | Find commits authored by a given login in a repo. Returns SHAs (identical across GitHub and GitLab, invariant #5) with a REST path to fetch each — so you can cross-reference against either provider. |
| get_snapshotA | Return the pinned, reproducible hostname for a provider — point your client's base URL at it for drift-free CI. A snapshot regenerates byte-identically on every request. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
The data tools each target a distinct resource+action (repositories, pull requests, issues, users, commits), and the three meta tools (orient, get_snapshot, check_budget) serve clearly different setup/reproducibility/budget purposes. Minor risk that orient overlaps conceptually with check_budget and get_snapshot as 'introspection' tools, but descriptions clearly separate them.
Nearly all tools follow a predictable verb_noun pattern (get_snapshot, check_budget, list_repositories, get_repository, list_pull_requests, get_pull_request, list_issues, get_user, search_commits_by_author). The lone bare verb 'orient' is a minor deviation from the otherwise consistent scheme.
Ten tools is well-scoped for a read-only multi-provider API surface with a few setup helpers. Each tool earns its place with no obvious redundancy or filler.
The read-only surface covers lists/gets for repositories and pull requests plus issues, users, and commit search, matching the stated read-only, snapshot-oriented purpose. Asymmetries remain (list_issues with no get_issue, get_user with no user list, no issue/PR comment retrieval), but agents can work around these via the returned REST paths.