MCP

Connect any MCP-compatible AI agent to Agentis wallets and financial tools.

Agentis Remote MCP gives AI agents scoped access to wallets, payments, policies, swaps, yield, portfolio data, and privacy tools on Solana.

For most users, Remote MCP is the recommended setup. It requires no local package, account key, or manual credential configuration.

Connect to Remote MCP

Add this URL as a remote or Streamable HTTP MCP server in your MCP-compatible client:

https://mcp.agentis.systems/mcp

Then:

1. Your MCP client opens the Agentis authorization page in your browser.
2. Sign in to Agentis and review the permissions requested by the client.
3. Approve the connection.
4. Return to your MCP client. The Agentis tools are now available to your agent.

The exact button names vary by client. Look for an option such as Add MCP server, Connect remote server, or Custom MCP server, then select Streamable HTTP and enter the URL above.

Verify the connection

Ask your agent:

List my Agentis wallets.

This calls the read-only agentis_list_agents tool. You can then try:

Show the balance and spending policy for my Agentis wallet named leno.

For a policy check that does not move funds:

Check whether leno is allowed to spend $1.

If a client needs scopes that were not granted during the original connection, reconnect it and approve the expanded permissions on the Agentis consent screen.

What your agent can do

Wallets and payments

• list and create hosted agent wallets
• read balances and transaction history
• send SOL after policy checks
• pay MPP and x402 protected APIs

Policies

• inspect and update spending policies
• run policy checks without spending funds
• initialize and read Quasar on-chain policy state

Policy amounts are USD-denominated.

Swaps, yield, and portfolio

• search Solana token metadata
• quote and execute policy-controlled swaps
• read Jupiter portfolio positions
• deposit into and withdraw from Jupiter Earn
• inspect Earn positions and sweep eligible USDC balances
• create, list, and cancel recurring orders

Jupiter operations use mainnet funds. Review the requested action, amount, and policy before approving a write operation.

Privacy

• register an agent with Umbra
• inspect encrypted balances
• deposit and withdraw supported assets
• create receiver-claimable UTXOs
• scan and claim private transfers

Umbra tools currently operate on supported hosted agent wallets.

Security and authorization

Remote MCP is a stateless Streamable HTTP service:

• access is authorized through Agentis OAuth
• access tokens are bound to the Agentis MCP resource
• clients receive only the scopes approved on the consent screen
• each OAuth grant can be revoked independently
• the MCP Worker does not store your Agentis account credentials
• hosted wallet signing remains inside Agentis

OAuth access tokens are refreshed by compatible clients using the associated refresh grant. You can reconnect if your client loses or revokes its session.

Local stdio

Local stdio remains available for clients that cannot connect to remote Streamable HTTP servers. It requires an Agentis account key on the same machine as the MCP process.

Install the package:

bun add -g @agentis-hq/mcp

Configure your local MCP client:

{
  "mcpServers": {
    "agentis": {
      "command": "agentis-mcp",
      "env": {
        "AGENTIS_ACCOUNT_KEY": "agt_user_..."
      }
    }
  }
}

Set AGENTIS_API_URL only when targeting a local or staging backend:

{
  "env": {
    "AGENTIS_ACCOUNT_KEY": "agt_user_...",
    "AGENTIS_API_URL": "http://localhost:3001"
  }
}

Local stdio uses an account API key for compatibility. Remote MCP uses OAuth and does not require an account key.

Local encrypted-wallet vault signing is intentionally CLI-only. MCP tools operate hosted Agentis wallets.