A company is a folder named by its handle, holding who you are, every way into your product, and one file per function an agent can call.
Note. The handle is permanent: it becomes your URL and the first half of every tool key. A rename only ever redirects.
How to create
1. Choose the handle
Lowercase letters, digits and hyphens, 2–39 characters, and not a reserved word such as tools, workflows or mcp. It becomes your company URL and the first half of every tool key, and it is permanent — a rename only ever redirects.
companies/apollo/ company.md tools/enrich-person.md2. Write company.md
Name, bare domain with no scheme, a category listed in tags.yml, a logo file you add to public/logos/, and the date you checked the facts. The body is a short description. Optional fields are shown when present — leave out anything you cannot verify publicly.
companies/apollo/company.md --- name: Apollo domain: apollo.io category: data-provider tagline: Contact data, work emails and outbound sequences in one place. docs: https://docs.apollo.io github: https://github.com/apolloio logo: apollo.webp mcp: url: https://mcp.apollo.io/mcp auth: oauth docs: https://docs.apollo.io/docs/apollo-mcp cli: install: brew install apolloio/apollo-io-cli/apollo-io-cli binary: apollo auth: oauth docs: https://docs.apollo.io/docs/apollo-cli-overview api: url: https://api.apollo.io/api/v1 auth: api_key env: APOLLO_API_KEY header: x-api-key keyUrl: https://developer.apollo.io/#/keys docs: https://docs.apollo.io/reference/apollo-api updated: 2026-09-26 --- Apollo is a sales intelligence and engagement platform with a database of over 240 million contacts and 30 million companies. Its MCP server, the `apollo` CLI and the REST API search and enrich people and companies, manage contacts, accounts and deals, and enroll contacts in outbound sequences. The MCP server and the CLI sign in with OAuth; the API takes an API key, and the Apollo plan decides which endpoints it can call and what they cost in credits.3. Say how an agent reaches you
In the same header, mcp:, cli: and api: describe each door into your product, once, for every tool to share: the MCP server’s URL or command, the CLI’s install command and binary, the API’s base URL — each with how it authenticates. An API key names the environment variable it goes in, never the key. Community-run doors say who maintains them.
companies/stripe/company.md --- name: Stripe domain: stripe.com category: payments tagline: Payments, billing and subscriptions for internet businesses. docs: https://docs.stripe.com github: https://github.com/stripe logo: stripe.jpg mcp: url: https://mcp.stripe.com auth: oauth docs: https://docs.stripe.com/mcp cli: install: npm install -g @stripe/cli binary: stripe auth: oauth docs: https://docs.stripe.com/stripe-cli api: url: https://api.stripe.com auth: api_key env: STRIPE_API_KEY keyUrl: https://dashboard.stripe.com/apikeys docs: https://docs.stripe.com/api updated: 2026-09-27 ---4. Add one file per function
Every function an agent can call gets its own file under tools/, named after the function and naming its exact call on each way in. That is the "Add a tool" guide, repeated once per function.
companies/apollo/tools/enrich-person.md companies/apollo/tools/search-people.md companies/apollo/tools/enrich-company.md5. Check it locally
One command parses every file, resolves every reference and renders the result. It reports every problem at once, each with the file that caused it (and the line, for a problem in the body). The same checks run again in CI on your pull request.
pnpm install pnpm content:check pnpm dev # then open /companies/apollo6. Open a pull request
One company, tool or workflow per pull request keeps the review quick. Say what you added and how you checked the facts. Maintainers review for accuracy, not for style — the build owns style.