Skip to main content
Provider capabilities read data from the accounts connected to a project, such as deployments, logs, CI failures, and issues. API clients, the CLI, and MCP agents ask Squasher, and never handle provider tokens directly.

​
GitHub activity

Returns recent commits and pull requests for the project’s default linked repository. To read another linked repository, pass repo (owner/name). The response lists every linked repository in repositories.

​
GitHub CI failures

Returns recent GitHub CI failure groups that Squasher has already ingested for the project. Use limit, branch, repo, and since to narrow the result set.

​
Linear issues

Returns recent issues for the Linear team configured on the project.

​
Notion pages and data sources

The connect endpoint returns the Notion page-picker URL. Search accepts query, kind, cursor, and page_size. Data-source paging accepts cursor and page_size. Page block reads recurse with fixed depth, block, response-size, and pagination limits.

​
Railway deployments and logs

Use service and environment when the bound Railway project has more than one target. Restart and redeploy are dangerous operations and should be confirmed by the caller.

​
Vercel deployments and logs

Common query parameters include deployment_id, branch, environment, state, query, and limit. Runtime logs also accept level, source, request_id, status_code, since, and until.

​
Agent handoff

Use provider capability endpoints when the project has an integration connected and the agent needs project-scoped context:
CLI equivalents live under squasher providers .... MCP clients should call search("providers") or the exact operation id, then execute with the selected project and filters.