Millbase MCP
Your AI agent, connected to your operation.
Ask ChatGPT or Claude about your projects, warehouse, and team. Millbase MCP gives your agent read-only tools to retrieve live data from your organization.
Connect your agent
You’ll need administrator access to your Millbase organization and a client with custom MCP support. Copy this server URL, then follow the steps for your agent.
https://app.millbase.ca/api/mcpConnect ChatGPT
OAuth sign-inAdd a custom MCP server
In ChatGPT, open Plugins → + → Add custom MCP server. Some workspaces show this under Apps. If the option is missing, ask your workspace administrator to enable custom MCP connections.
Enter the Millbase connection
Name it Millbase, paste the server URL above, and select OAuth. Choose ChatGPT’s published client identity (CIMD) if asked. No API key or client secret is needed.
Sign in and choose your organization
Complete the Millbase sign-in, select the organization, review the read permissions, and approve. Return to ChatGPT and enable Millbase in your conversation.
Connect Claude
OAuth sign-inAdd a custom connector
Open Customize → Connectors in Claude (or Settings → Connectors in earlier layouts). Choose + Add → Add custom connector.
Add Millbase and sign in
Enter Millbase as the name and paste the server URL above. Continue with OAuth and Sign in now. If offered an OAuth client choice, use Claude’s published identity.
Approve organization access
Sign in to Millbase, select the organization, and approve the read permissions. In a Claude conversation, open + → Connectors and enable Millbase.
Connect Claude Code
API keyCreate and save your key
Generate a Millbase API key with the read permissions you need. Replace the placeholder and set it in the terminal where you run Claude Code.
Terminalexport MILLBASE_API_KEY='YOUR_MILLBASE_API_KEY'Register the server
With the Claude Code CLI installed, run this command. User scope makes Millbase available across your projects. The command saves the resolved key in your local Claude configuration; keep that file private.
Terminalclaude mcp add --transport http --scope user millbase \ https://app.millbase.ca/api/mcp \ --header "Authorization: Bearer $MILLBASE_API_KEY"Check the connection
Start Claude Code, run /mcp, and confirm Millbase is connected. Then ask it to list your Millbase resources.
Connect Grok Bot
Connect from chatAsk your Bot to add Millbase
Open a conversation in Grok Bot and send this message. The Bot can add a remote MCP server directly from its URL.
MessageAdd Millbase as a remote MCP server: https://app.millbase.ca/api/mcp Guide me through authentication, then list the Millbase resources I can access.Authorize the connection
Follow the Bot’s Connect or Authenticate card. If it opens Millbase sign-in, select your organization and approve the read permissions. If an API key is requested, create a dedicated Millbase key and enter it in Grok Bot’s secure secret card, not the chat.
Confirm Millbase is ready
Open Connect apps and confirm Millbase appears under Installed and is authenticated. Ask your Bot to list your Millbase resources, then your projects. Grok Bot needs an eligible subscription; your team may also need to allow custom connectors.
Connect Muse
Custom connectorMuse creates custom connectors from a service’s documentation. Ask it to use Millbase MCP when supported, or the Millbase API for the same live organization data.
Ask Muse to create the connector
Send this message in Muse. It includes the server URL and public documentation so Muse can guide the setup.
MessageCreate a read-only Millbase custom connector. MCP server: https://app.millbase.ca/api/mcp MCP guide: https://millbase.ca/docs/mcp API guide: https://millbase.ca/docs/api Use remote MCP if supported; otherwise use the API. Request my API key through your secure credential flow and use Bearer authentication. Then list my projects and their statuses.Add a dedicated Millbase key
Generate an API key in the Millbase organization you want Muse to read, with only the permissions it needs. Enter it through Muse’s secure credential flow when prompted. Keep the key out of ordinary chat messages.
Review and try the connector
Review the connector’s read-only actions and approve the setup. Ask Muse to list your Millbase projects. Manage or disconnect it in Settings → Connectors; revoke its API key in Millbase to stop access.
Connect Perplexity
API keyCreate a key for Perplexity
Generate a Millbase API key in the organization you want to connect. Name it Perplexity and select the read permissions you need.
Add a remote MCP connector
In Perplexity, open Plugins → Add custom → Add MCP connector, then select Remote. Earlier layouts use Customize → Connectors. Name the connector Millbase and paste the server URL above.
Set authentication and transport
Under Advanced, choose API Key authentication and enter your Millbase key in the API key field. Select Streamable HTTP and Public network access. Review the acknowledgement, then select Add and enable the connector.
Ask about your projects
Ask: “Using Millbase, list my projects and their statuses.” If custom connectors are disabled, ask your Perplexity administrator to enable them. Use a connector for your own account unless you intend to share its access with your Perplexity organization.
Connect a compatible MCP client
Streamable HTTPUse a client that supports a remote Streamable HTTP server and custom request headers. Set the server URL above and send Authorization: Bearer YOUR_MILLBASE_API_KEY on each request. The client handles MCP initialization and tool calls.
Here is an alternative Claude Code .mcp.json configuration that reads your environment variable. Other clients use different configuration formats; follow their documentation for secret storage and variable substitution.
{
"mcpServers": {
"millbase": {
"type": "http",
"url": "https://app.millbase.ca/api/mcp",
"headers": {
"Authorization": "Bearer ${MILLBASE_API_KEY}"
}
}
}
}Set MILLBASE_API_KEY before starting the client. OAuth is configured for ChatGPT and Claude; a different OAuth client may need registration. A generic MCP client’s compatibility does not guarantee support in every agent product.
Your agent provider’s plan and workspace permissions may affect connector availability. Millbase hosts the server; you do not need to run one locally.
Ask your first question
Start with discovery, then ask a specific question. Your agent chooses the right Millbase tool and reads the records needed to answer.
List the Millbase datasets I can access, then show the names and statuses of my projects.
Show my current warehouse inventory with each material’s name, unit, and quantity on hand.
Find my project by name, then summarize its recorded labor hours for last week. Tell me which dates you used.
Be explicit about project names and date ranges. Cost or people questions require those read permissions. If the organization has no matching records, an empty result is expected.
One data source. Two ways in.
The API is the entrance for software. MCP is the entrance for AI agents. Both use the same permission checks and query service to read the same live Millbase database.
MCP translates an agent’s tool call into that shared query service. It does not maintain a separate copy of your data or require an extra public API round trip. Each request reads current stored records; it is not a continuous live stream.
Two tools, clear capabilities
list_resources
Lists the datasets, fields, and required permissions available to the connection. No arguments required. Your agent should start here.
query_data
Reads rows using resource, fields, filters, limit, and offset. It supports the same query shape and pagination as POST /api/v1/query.
{
"resource": "materials",
"fields": [
"id",
"name",
"unit",
"on_hand"
],
"limit": 50,
"offset": 0
}Explore all datasets and fields · Learn filters and pagination
Your organization stays the boundary
Every call checks access and permissions. These tools cannot create, edit, or delete records. Only allowed datasets and fields are returned. Your AI provider receives the tool results you authorize it to read.
Disconnect whenever you need
In Millbase, go to Settings → API and integrations → MCP. Revoke an OAuth connection to block that agent’s access to the organization. Connections appear after their first authenticated request. For an API-key client, revoke its key in the API keys tab.
MCP shares the API’s rate and monthly limits. Agent discovery and tool calls consume requests. Your AI provider’s own subscription and usage charges are separate. View limits.
If something doesn’t connect
I can’t find the custom connector option.
Check your agent provider’s plan and workspace settings. An administrator may need to enable custom MCP servers. Use the provider’s setup guide linked above for the current interface.
Sign-in succeeds, but a query is denied.
Confirm you selected the correct Millbase organization and still have administrator access. Check the granted scopes. Reconnect to approve missing permissions. If ChatGPT offers optional OpenID Connect scopes and reports an unsupported scope, turn that optional setting off and reconnect with OAuth.
The server URL returns an error in my browser.
The MCP URL is a protocol endpoint, not a web page. Add it to an MCP client with OAuth or a Bearer API key. An ordinary browser visit is not a connection test.
My agent returns no records or stops partway through.
An empty result can be valid. Check the chosen organization, filters, and permissions. For larger datasets, ask the agent to continue with pagination.nextOffset. If rate-limited, wait for Retry-After before trying again.