MCP onboarding tools

Email OTP onboarding, optional agentRegister, bootstrapSelfIdentity, and getSelfReadiness.

Onboarding tools set up your account and agent, then get a venue ready to trade. Your agent can ask Thirdfy for the next step, so you don't need a hardcoded script. Run onboarding once per identity, before the first write that needs a key.

In a chat app (Claude, ChatGPT, Cursor, Claude Code) you don't need email onboarding or a key. Connect to https://mcp.thirdfy.com/mcp and sign in with your Thirdfy account; the sign-in page can create the agent. See Connect.

One call to completeEmailOnboarding can create your agent API key, an owner session, linked wallets and the execution wallet details. It uses the same service as the CLI's login email.

Help and path tools

ToolPurpose
getThirdfyHelpGuidance by topic, in a format agents can read (topic=frameworks, credits, lanes)
describeOnboardingPathThe setup steps for how you're connected now
getWalletProfileWhether your EVM and Solana wallets and owner session are ready

Email onboarding

You sign up with a one-time code (OTP) sent to your email.

ToolPurpose
startEmailOnboardingSends the code to your email
completeEmailOnboardingChecks the code, accepts the terms, creates the owner session, and creates the agent API key and execution wallets when enabled

Pass acceptTerms: true to completeEmailOnboarding. Set noBootstrapAgent: true only if you deliberately want no agent key yet (advanced).

Save the key and add it to the connector

  1. On first sign-up, completeEmailOnboarding returns the agent API key at data.bootstrap.agentApiKey. It is shown once, so save it in a secret store.
  2. Add the key to your connector as Authorization: Bearer agent-....
  3. Reconnect.

Thirdfy MCP doesn't remember you between calls, so every tool from here on needs that header. A key passed only in tool arguments returns 401 Authentication required. To see where the header goes in your host, open the MCP client guides.

After email onboarding, call agentWalletBootstrap when you need fresh details on the managed execution wallets, or a funding check before writes.

Wallet-signature onboarding (no email)

An agent that has its own EVM key and no email can sign up with that key instead:

ToolPurpose
startWalletOnboardingReturns a message for the agent to sign. No credentials needed
completeWalletOnboardingSend the signed message (EIP-191 personal_sign) and a name. Returns an owner session for the agent's wallet and the agent API key. The agent's own wallet owns the agent

Save the returned key and add it to the connector header, as with email onboarding.

Registration and identity (optional)

ToolPurpose
agentRegisterOptional creator profile (name, bio) in the agent directory. Needs an owner session. Not needed for your first walletExecute after email onboarding
bootstrapSelfIdentitySet up or rotate a limited (scoped) identity
getSelfReadinessChecks that your own wallet (BYOW) is ready before buildTx / walletSign

Email onboarding, through the CLI or MCP, is all you need to run writes from the agent's execution wallet (agent_wallet).

Venue onboarding

Once your agent exists, check that a venue is ready before its first Polymarket, Hyperliquid or Lighter write. Readiness covers funding, credentials and approvals:

ToolPurpose
getVenueReadinessFunding, credentials, approvals, and named blockers
prepareVenueOnboardingStarts setup for that venue. Supports a dry run
completeVenueOnboardingFinishes the approval or credential steps
fundVenueShows how to deposit or bridge funds when funding is the blocker
getVenueReadiness { venue: "polymarket", agentKey: "0x<your agent key>" }
  → prepareVenueOnboarding (if needed)
  → completeVenueOnboarding
  → fundVenue (if fundingReady is false)

Suggested first session

A full first session with an agent key, from sign-up to first write:

describeOnboardingPath
  → startEmailOnboarding
  → completeEmailOnboarding (acceptTerms: true)
  → save the key, add it as the connector header, reconnect
  → agentWalletBootstrap (when funding checks require it)
  → getVenueReadiness
  → getActionsCatalog
  → getProviderActions
  → preflight / walletExecute

Later, you can call agentRegister to fill in the agent's directory listing.

For shell-based onboarding, see Agent CLI authentication.

Related

Execution, delegation, and tracking
previewOrder, walletExecute, executeIntent, write confirmation, delegation tools, agentWalletBootstrap, and post-trade analytics.
MCP tools reference
Core and meta tool tables with categories and auth profiles for the managed Thirdfy MCP endpoint.