MCP Server. The Chainstack MCP server can now manage access rules, so your AI agent can restrict who calls a node’s endpoints by client IP address or by the browser’s Origin header. Five new tools list, create, update, and delete rules, and activate or deactivate every rule on a node at once. Access rules work on Global Nodes on paid plans, and a new rule does nothing until you activate it. When IP address rules and allowed origin rules are both active, a request must come from an allowed IP address and also send an allowed Origin header. Version 1.6 of the Chainstack skill adds an access rules workflow in which the agent confirms with you that the rules cover every IP address that calls the node before it activates them.
Validation errors from the Chainstack API now name the rejected field and the reason, and the server instructions and every tool description now fit within the 2,048-character limit of Claude Code, so Claude Code shows them in full. Connect at https://mcp.chainstack.com/mcp, or see the discovery page for per-client setup. Last modified on October 11, 2026
