Model Context Protocol

Bring trusted ingredient context into your AI workflow.

Connect MCP-compatible assistants and agents to the same context-aware ingredient database used by CleanBites search. Look up names, aliases, regulatory identifiers, concerns, and references without leaving your conversation.

Available tools

Three tools, one reliable data source

Each tool follows the same conservative matching and context safeguards as the CleanBites website.

search_ingredients

Search by ingredient name, alias, CAS number, E-number, UNII, or DTXSID, with optional category and concern filters.

autocomplete_ingredients

Return fast, consumer-facing ingredient and alias suggestions for a partial search term.

get_ingredient

Retrieve a full ingredient record by slug or UUID, including aliases, references, concerns, and guidance.

Integration guide

Connect in three steps

CleanBites uses Streamable HTTP and Bearer-token authentication. Your MCP client may use a different settings file, but the endpoint and authorization header stay the same.

1
Get an access token
Register for a CleanBites account to receive a personal token immediately. Already registered? Manage tokens from your account.
2
Add the remote server
Add the MCP endpoint and authorization header to your client, using the configuration shown here as a starting point.
3
Start asking
Once connected, your assistant can discover and call all three CleanBites tools automatically.

MCP client configuration

JSON

{
  "mcpServers": {
    "cleanbites": {
      "url": "https://cleanbites.net/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_CLEANBITES_TOKEN>"
      }
    }
  }
}

Try it out

Example prompts

Search CleanBites for E621 and explain the result in plain language.
Find ingredients matching sodium benzoate in a food context.
Get the complete CleanBites record for citric acid, including references.