Skip to main content

Core web: How do I configure the Core MCP?

How to configure the Core MCP server in Core web — accounts, networks, spend limit, and allowed recipients.

C
Written by Chris

The MCP Configuration menu in Core web lets a user control how an AI agent can access their wallet through the Core MCP server, including which accounts and networks are available, a daily spend limit, and which recipients are allowed.

The MCP Configuration tool and enabling AI access

  1. Open core.app.

  2. Select Connect Wallet, using Sign in with Google/Apple.

  3. Click the Settings gear in the top right.

  4. Click AI Connectors.

  5. Toggle Enable AI Access to allow an AI agent to access the wallet through the Core MCP.

  6. For examples on connecting to the MCP, see this article.

Set spend limit

NOTE: This sets a rolling 24-hour spend limit for the MCP connector; it will not be able to go over the set limit. The limit is per wallet not per account.

  1. Click Spend Limit.

  2. Type in a $ value or use the $50, $100, $250, or No Limit buttons.

  3. Click Update Limit to save the configuration.

WARNING: No Limit disables the rolling 24-hour USD limit on every transaction signed through this MCP server. With No Limit, the connected AI agent can sign and broadcast transactions of any value, up to the entire balance of each policy-enabled account, without that safeguard in place. A single mistaken, unexpected, or malicious instruction could result in the total loss of a user's funds. Only set to No Limit if you fully understand and accepts this risk.

Enable or disable accounts for MCP use

NOTE: This setting determines whether seedless accounts on the wallet are enabled for use by the MCP. Only policy-enabled accounts can sign transactions.

  1. Click Accounts.

  2. Check or uncheck the Accounts to enable for MCP use.

  3. Click Update to save the configuration.

Set allowed recipients

NOTE: This setting allows a user to set the connector to allow any address, or to allow a list of specific addresses (set by the user) to send assets to. This policy is only enforced for send transactions involving following asset types:

  • Native network tokens

  • ERC20s (EVM)

  • SPL tokens (Solana)

If the asset is not one of the above, it will not be subject to this allow list policy. See this article for more information.

  1. Click Allowed Recipients.

  2. Choose Custom Recipients or Any Address (Higher risk).

    • If Custom Recipients, click Manage Custom List.

    • Add a Name and at least one eligible address.

    • Click Save.

  3. Click Save.

WARNING: Setting the recipient allowlist to Any Address removes the restriction that limits transactions to approved destinations. With this setting, the connected AI agent can send a user's funds to any address on any enabled network. A single mistaken or malicious instruction could move funds to an irreversible destination. Only set to Any Address if the user fully understands and accepts this risk.

Enable or disable networks

NOTE: This setting determines which of the eligible networks the agent can operate on.

  1. Click Networks.

  2. From the drop-down, check or uncheck any Network, or check Enable All Networks.

  3. Click off the Networks menu.

Disclaimer

The Core Knowledge Base, including all the Help articles on this site, is provided for technical support purposes only, without representation, warranty, or guarantee of any kind, and is not technical, investment, financial, accounting, tax, or legal advice. The Core Wallet MCP Server enables an authorized AI agent to sign and broadcast transactions from your wallet. The spend-policy controls described above are provided on a best-efforts basis, apply only to the transaction types and networks specified, and do not guarantee against loss — including loss resulting from agent behavior, network fees, failed or unavailable simulation, or transactions falling outside the scope of a given control. You are responsible for the accounts, recipients, networks, limits, and agents you choose to enable. Examples are illustrative only. Please review this Notice and the Terms of Use.


For any additional questions, please view our other knowledge base articles or contact a Product Support team member via the chat button. Examples are for illustrative purposes only.

Did this answer your question?