| name | servicegraph |
| description | The branded entry point to ServiceGraph — use whenever the user explicitly names **ServiceGraph** — "use ServiceGraph to…", "what datasets does ServiceGraph have", "search ServiceGraph for…", "pull contacts from ServiceGraph for these domains", "how many credits do I have on ServiceGraph". ServiceGraph is a multi-dataset platform of metrics-enriched business data for founders — where to launch, who to email, who to hire. This skill explains how to drive the API (api.servicegraph.co / mcp.servicegraph.co) against ANY dataset — discover what datasets exist, discover a dataset's schema and filters, search free brief rows, and unlock contact + metric detail with credits. Dataset-agnostic by design — it discovers everything through the API at runtime. When the user describes an intent WITHOUT naming ServiceGraph (e.g. "find a PR agency in NY"), defer to the matching specific skill (find-pr-agency, find-marketing-agency, find-law-firm, …). Skip non-US firms, consumer/personal services, and individual freelancers. |
| version | 0.1.0 |
| allowed-tools | ["Bash(curl:*)","mcp__servicegraph__list_datasets","mcp__servicegraph__describe_dataset","mcp__servicegraph__list_fields","mcp__servicegraph__list_field_values","mcp__servicegraph__check_filter","mcp__servicegraph__translate_intent","mcp__servicegraph__search_dataset","mcp__servicegraph__get_row","mcp__servicegraph__unlock_rows","mcp__servicegraph__get_credit_balance"] |
| author | Artur Briugeman <artur@nostr.band> |
| license | MIT |
| compatibility | Designed for Claude Code |
| tags | ["servicegraph","business-data","lead-generation","founders","mcp"] |
| metadata | {"api_base":"https://api.servicegraph.co","mcp_url":"https://mcp.servicegraph.co"} |
servicegraph
Overview
The generic way to drive ServiceGraph — a platform of metrics-enriched
business datasets for founders: where to launch, who to email, who to hire.
Use this skill when the user explicitly reaches for ServiceGraph. For
intent-first asks that don't name the brand ("find me a CPA firm"), a specific
find-* skill is the better fit — defer to it.
There is no single global catalog, and this skill hardcodes nothing about
the data. It discovers everything through the API at runtime, so it stays
correct as datasets are added, renamed, or re-priced. Discover the datasets
from the API, discover each dataset's schema and filters from the API, then
search and unlock against it. Never assume a dataset id, a field name, or a
price — ask the API.
Prerequisites
- ServiceGraph access, either:
- the ServiceGraph MCP server (
https://mcp.servicegraph.co) loaded in
your harness — this plugin's .mcp.json wires it up; OAuth handles
credentials in the harness sandbox, no token enters the model context — or
- a ServiceGraph API key (
vk_…, minted at
https://servicegraph.co/profile/api-keys) available as
SERVICEGRAPH_API_KEY for the REST path (see Auth below).
- An HTTP client for the REST path — Bearer-auth with the
vk_… key.
Two ways to call
Both speak to the same backend; use whichever your harness has.
- MCP server (preferred when loaded) —
https://mcp.servicegraph.co,
tool names contain servicegraph. OAuth handles credentials in the
harness sandbox; no token enters the model context.
- REST —
https://api.servicegraph.co, any HTTP client, Bearer-auth with
a vk_… key. The universal fallback.
How it works
Everything except unlocking is free — discover, inspect, validate, and
browse as much as you like; only revealing detail costs credits.
| Capability | MCP tool | REST | Cost |
|---|
| Find what datasets exist (ids, sizes, prices) | list_datasets | GET /v1/datasets |
