# How to connect PocketSmith to OpenClaw (paste one key, 14 tools) > Connect PocketSmith to OpenClaw with ClawLink: paste your PocketSmith key once and 14 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/pocketsmith The usual route to PocketSmith access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical PocketSmith setup: install one ClawHub skill, connect PocketSmith in the browser, and OpenClaw can call real PocketSmith actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to PocketSmith. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect PocketSmith** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect pocketsmith # connect PocketSmith (browser OAuth) npx -y @useclawlink/cli actions pocketsmith # list available actions npx -y @useclawlink/cli run pocketsmith --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect PocketSmith in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your PocketSmith API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from PocketSmith, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once PocketSmith is connected in the dashboard, that agent calls the same 14 PocketSmith tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## PocketSmith MCP for OpenClaw Looking for a PocketSmith MCP server for OpenClaw? ClawLink connects PocketSmith to OpenClaw and exposes 14 PocketSmith tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes PocketSmith integration](https://claw-link.dev/hermes/pocketsmith) works the same way. ## What the OpenClaw PocketSmith integration can do 14 PocketSmith tools are ready for OpenClaw once the account is connected. ### All 14 PocketSmith tools for OpenClaw | Tool | What it does | |---|---| | **Get budget** `pocketsmith_get_budget` | Return a PocketSmith user's current category-level actual and forecast budget analysis | | **Get budget summary** `pocketsmith_get_budget_summary` | Analyze the user's combined income and expense budget over a required date range and period | | **Get current user** `pocketsmith_get_current_user` | Return the PocketSmith user authorized by the connected developer key, including the user ID | | **Get transaction** `pocketsmith_get_transaction` | Return one PocketSmith transaction by ID with its amount, date, payee, category, labels, and | | **List accounts** `pocketsmith_list_accounts` | Return all financial accounts belonging to a PocketSmith user, including account, primary | | **List categories** `pocketsmith_list_categories` | Return all categories belonging to a PocketSmith user, including hierarchy and budgeting flags | | **List transaction accounts** `pocketsmith_list_transaction_accounts` | Return the transaction accounts belonging to a PocketSmith user, including IDs and balances | | **List transactions** `pocketsmith_list_transactions` | Return one page of a user's transactions with optional date, state, type, and keyword filters | | **Create category** `pocketsmith_create_category` | Create one category for a PocketSmith user with optional hierarchy and budgeting behavior | | **Create transaction** `pocketsmith_create_transaction` | Create one transaction in a specified transaction account and return the created financial | | **Update account** `pocketsmith_update_account` | Update selected metadata on one financial account without deleting it or changing | | **Update category** `pocketsmith_update_category` | Update selected hierarchy, display, and budgeting fields on one category without deleting it | | **Update transaction** `pocketsmith_update_transaction` | Update selected fields on one existing transaction without deleting or splitting it | | **Update transactions** `pocketsmith_update_transactions` | Update 1-20 distinct transactions sequentially | ## Example prompts **Get Budget** > Pull the relevant data from PocketSmith, summarize it in plain English, and point out anything that needs attention. **Get Budget Summary** > Pull the relevant data from PocketSmith, summarize it in plain English, and point out anything that needs attention. **Get Current User** > Pull the relevant data from PocketSmith, summarize it in plain English, and point out anything that needs attention. **Get Transaction** > Pull the relevant data from PocketSmith, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want PocketSmith working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the PocketSmith API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected PocketSmith account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for PocketSmith. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right PocketSmith actions to the runtime in a format your agent can reliably use. | 14 tools for PocketSmith are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes PocketSmith to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect PocketSmith in the browser, and the 14 tools above work from chat. There is no SDK and no config file, and the PocketSmith key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the PocketSmith skill but can't call the tools The ClawHub skill teaches OpenClaw about PocketSmith, but the calls run through the ClawLink plugin and your connected account. Make sure PocketSmith is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect PocketSmith from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling PocketSmith tools PocketSmith tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every PocketSmith call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### PocketSmith returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for PocketSmith has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw PocketSmith integration? Yes. ClawLink is the fastest way to connect OpenClaw to PocketSmith: link your PocketSmith account once in the browser and OpenClaw can call the PocketSmith API through 14 ready-made tools — no custom code or token handling. ### How do I add PocketSmith to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink PocketSmith skill from ClawHub, then you click Connect in the dashboard to authorize PocketSmith. OpenClaw calls the tools from the next message — no config files, and the PocketSmith key you paste is stored server-side instead of in your environment. ### How long does it take to connect PocketSmith to OpenClaw? About two minutes. Sign in, click Connect next to PocketSmith in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring PocketSmith up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want PocketSmith working from chat. ### OpenClaw installed the PocketSmith skill but can't call the tools The ClawHub skill teaches OpenClaw about PocketSmith, but the calls run through the ClawLink plugin and your connected account. Make sure PocketSmith is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [Connect PostHog](https://claw-link.dev/openclaw/posthog) — Track user behavior and feature flags - [OpenClaw DataforSEO integration](https://claw-link.dev/openclaw/dataforseo) — SEO data APIs for keywords, SERP, and site audits - [Metabase](https://claw-link.dev/openclaw/metabase) — Metabase is an open-source business intelligence tool that lets you ask questions about your data and visualize answers as charts, graphs, and dashboards.