Connect your agents.
Every TomorrowCentral tool ships an MCP server — the same tool your team clicks in the console, exposed for agents to call. No glue code, no bespoke integration.
How it works
From token to tool call in four steps.
Step 1
Create an API key
Generate a scoped API key for your agent from your dashboard. Revoke it anytime.
Step 2
Add the MCP server
Point your MCP client at the TomorrowCentral MCP server and pass your API key. That's the whole setup.
Step 3
Your agent discovers it
The server advertises every tool's actions and inputs over MCP — your agent sees exactly what it can do.
Step 4
It runs, safely
Calls execute under your scoped role and tenant. No stored credentials, full isolation, results returned to the agent.
Add the server
One entry in your MCP client.
Add the TomorrowCentral MCP server to your agent's config with your API key. Your agent discovers every tool's actions automatically and calls them under your scoped role.
Works with any MCP-compatible client. One server exposes all your tools — create an API key in your dashboard.
Every tool, input, output, limit and AWS permission is documented in the agent reference.
{
"mcpServers": {
"tomorrowcentral": {
"url": "https://api.tomorrowcentral.com/mcp",
"headers": {
"X-Api-Key": "<your-api-key>"
}
}
}
}Scoped & revocable
Agents act under an API key and role you control. Revoke either at any time.
Same tool, same tenant
MCP calls run the identical tool your console does, isolated to your tenant.
No stored credentials
We assume your cross-account role for short-lived access — nothing long-lived is kept.