Geckoboard Metrics
com.geckoboard.gatewayPublished by gateway.geckoboard.comOfficial publisherv1.0.0Updated Oct 24, 2026
Query live metrics and data lists from the business tools connected to your Geckoboard
Overview
A remote Geckoboard MCP server that lets an assistant query live metrics and data lists from the business tools connected to your Geckoboard account.
- What you can do
- Query live metrics from the business tools connected to your Geckoboard account, so an assistant can report current figures on request. Retrieve data lists from those connected sources. The manifest lists no individual tools, so the exact operations are not documented here; the server is reached over a remote HTTP endpoint rather than run locally.
- When to use it
- Useful when you already use Geckoboard to track business metrics and want an assistant to pull current values or data lists into a conversation without opening dashboards manually.
- Requirements
- A remote endpoint at gateway.geckoboard.com, reached over streamable HTTP. OAuth authentication is required, so the user must sign in and authorize access to their Geckoboard account. No environment variables or headers are declared.
Installation
In SourceWeft
- Open Geckoboard Metrics in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.geckoboard.gateway%2Fmetrics/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"geckoboard-metrics": {
"type": "http",
"url": "https://gateway.geckoboard.com/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 18, 2026
Score
56% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.