QUICK START
Connect in three steps.
- 1Create a token
Open Websites, choose MCP after Settings & integrations, name the client, and choose its permissions.
- 2Copy it once
The secret appears only after creation. Save it directly in your MCP client.
- 3Add the remote server
Use the endpoint above with Streamable HTTP and send the token in the Authorization header.
This release works with MCP clients that support remote Streamable HTTP servers and custom Bearer headers. Clients that require an OAuth sign-in flow are not supported yet.
CONFIGURATION
Use a Bearer token on every request.
Client settings differ, but the connection has three stable values:
- Transport
- Streamable HTTP
- Server URL
https://api.indextoast.com/mcp- Header
Authorization: Bearer it_mcp_…
Generic configuration example
{
"mcpServers": {
"indextoast": {
"type": "streamable-http",
"url": "https://api.indextoast.com/mcp",
"headers": {
"Authorization": "Bearer it_mcp_YOUR_TOKEN"
}
}
}
}Your client may use http instead of streamable-http. Follow its naming convention while keeping the endpoint and header unchanged. Never put the token in the URL.
PERMISSIONS
Give each client only the access it needs.
Removing a permission takes effect on the next token you create. Revoke an existing token immediately if its access is no longer appropriate.
TOOLS
Everything available to the client.
get_account_overviewRead plan capacity and the current Indexing unit balance.Readlist_websitesList websites connected to the account.Readlist_batchesSearch submission and Index Check history.Readget_batchRead every URL and result in one batch.Readreview_standard_submissionValidate URLs and quote Standard usage.Reviewconfirm_standard_submissionSpend the quoted units and start the batch.Confirmreview_priority_submissionValidate URLs and quote Priority usage.Reviewconfirm_priority_submissionSpend the quoted units and start Priority processing.Confirmreview_index_checkValidate URLs and quote an Index Check.Reviewconfirm_index_checkSpend the quoted units and start the check.ConfirmMETERED ACTIONS
Review first. Confirm when the cost is clear.
IndexToast separates every metered action into two tools. A review validates and deduplicates up to 200 URLs, checks the live balance, and returns an exact quote without spending units. The matching confirmation accepts that unchanged confirmation object, reserves the units atomically, and starts the batch.
Confirmation calls are idempotent. Retrying the same confirmation does not charge the batch twice.
SECURITY
Access stays tied to one workspace.
- Tokens are scoped to the account that created them.
- Only a SHA-256 digest is stored by IndexToast.
- The full secret is displayed once.
- Tokens expire after 90 days and can be revoked immediately.
- Creation, revocation, and confirmed MCP batches are written to the audit log.
- Rate limits apply to the MCP endpoint and token creation.
TROUBLESHOOTING
Common connection problems.
The client receives 401 Unauthorized.
Confirm the header starts with Bearer, the full token was copied, and the token has not expired or been revoked.
A tool says a permission is required.
Create a new token with the named permission, update the client, then revoke the previous token if it is no longer used.
The client cannot add a custom header.
That client cannot use the current token-based connection. Use a compatible MCP client or wait for the planned OAuth connection flow.
A confirmation says the balance changed.
Run the matching review tool again. Another action may have used units after the original quote was prepared.
Does MCP use a different indexing provider?
No. MCP calls the same IndexToast submission and Index Check services as the dashboard, with the same provider routing, unit accounting, and batch history.
Ready to connect?
Create a scoped token, add the remote server, and ask your assistant to read your account overview.
Open MCP settings →