Add your company

List your company, how agents connect to it, and the tools it offers.

View on GitHub

A company is one folder named after its handle. It holds who you are, how an agent connects to your product, and one file for each action an agent can call.

Note. Your handle is permanent. It is your URL and the first part of every tool key. Renaming it only adds a redirect.

How to create

  1. 1. Choose the handle

    Use lowercase letters, numbers and hyphens, 2 to 39 characters long. Reserved words such as tools, workflows, docs or mcp are not allowed. The handle becomes your company URL and the first part of every tool key. It is permanent, so a rename only adds a redirect.

    companies/apollo/
    company.md
    tools/enrich-person.md
  2. 2. Write company.md

    Add name, your bare domain (no https://), a category from tags.yml, and updated, the date you checked the facts. The body is a short description. Optional fields only show when filled in, so leave out anything you cannot verify publicly. Add your logo next to it as logo.svg (or png, jpg or webp): your current icon, square, under 32 KB, with fixed colours. A maintainer moves it to our CDN before merging.

    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: https://cdn.growth.engineer/icons/companies/apollo-25ae17ed.png
    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. 3. Say how an agent reaches you

    In the same header, describe each way into your product once, under mcp, cli and api, so every tool can share it. Give the MCP server URL or command, the CLI install command and program name, or the API base URL, each with how it signs in. For an API key, name the environment variable it goes in, never the key itself. A remote MCP server signs in with oauth or needs none. If it needs a key, list your API instead. For a way in run by the community, name its maintainer.

    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: https://cdn.growth.engineer/icons/companies/stripe-5ba232e3.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. 4. Add your tools

    Every action an agent can call gets its own file under tools/, named after the action, with its exact call on each way in. Follow the “Add a tool” guide once for each one.

    companies/apollo/tools/
    enrich-person.md
    search-people.md
    enrich-company.md
  5. 5. Check it locally

    Run one command to check everything. It reads every file, checks every link and builds the pages, then lists every problem at once with the file (and line) that caused it. The same check runs again on your pull request.

    Terminal
    pnpm install
    pnpm content:check
    pnpm dev   # then open /companies/apollo
  6. 6. Open a pull request

    Send one company, tool or workflow per pull request. Say what you added and how you checked the facts. Reviewers check the facts, and the build handles formatting.