[{"data":1,"prerenderedAt":1662},["ShallowReactive",2],{"blog-post-openclaw-mcp-setup-guide":3,"related-posts-openclaw-mcp-setup-guide":823},{"id":4,"title":5,"author":6,"body":10,"category":797,"date":798,"description":799,"extension":800,"featured":801,"image":802,"imageHeight":803,"imageWidth":803,"meta":804,"navigation":805,"path":806,"readingTime":807,"seo":808,"seoTitle":809,"stem":810,"tags":811,"updatedDate":798,"__hash__":822},"blog/blog/openclaw-mcp-setup-guide.md","OpenClaw MCP Setup Guide: Connect 1,000+ Tools via Model Context Protocol (2026)",{"name":7,"role":8,"avatar":9},"Shabnam Katoch","Growth Head","/img/avatars/shabnam-profile.jpeg",{"type":11,"value":12,"toc":775},"minimark",[13,20,23,26,31,34,37,42,62,68,74,80,87,91,97,120,134,298,309,315,329,335,344,348,351,360,366,372,379,384,401,409,414,423,430,435,440,447,452,461,467,471,474,480,493,498,524,535,541,554,560,564,567,573,579,585,595,599,602,608,616,622,628,634,638,641,647,653,656,666,672,676,681,684,689,692,697,709,714,717,722,728,732,771],[14,15,16],"p",{},[17,18,19],"strong",{},"MCP is the reason your agent can read your GitHub repos, query your database, and search your Notion. Here's how to set it up on OpenClaw, the 5 servers worth installing first, and the security trap that comes with giving your agent access to everything.",[14,21,22],{},"Before MCP, connecting OpenClaw to GitHub meant writing a custom skill. Connecting to Notion meant writing another custom skill. Connecting to your database meant a third. Each skill had its own API contract, its own authentication pattern, and its own failure modes.",[14,24,25],{},"I spent a weekend building a GitHub skill that could read issues. It worked. Then I needed it to create PRs. That was a different API endpoint with different parameters. Another weekend.",[14,27,28],{},[17,29,30],{},"Two weekends for one integration that MCP handles in 30 seconds.",[14,32,33],{},"MCP (Model Context Protocol) is Anthropic's open standard for connecting AI agents to external tools. OpenClaw adopted it natively. As of May 2026, there are 1,000+ community-built MCP servers covering GitHub, Slack, Notion, PostgreSQL, Google Drive, Stripe, Jira, and hundreds more. The protocol was donated to the Linux Foundation's Agentic AI Foundation (AAIF), co-founded by Anthropic, Block, and OpenAI. It's no longer one company's standard. It's the industry's.",[14,35,36],{},"Here's how to set it up, which servers to install first, and the security considerations that most guides skip.",[38,39,41],"h2",{"id":40},"what-mcp-actually-does-the-60-second-version","What MCP actually does (the 60-second version)",[14,43,44,45,48,49,52,53,56,57,61],{},"MCP is JSON-RPC 2.0 over stdio or HTTP/SSE. That's it. A server exposes ",[17,46,47],{},"tools"," (functions the agent can call), ",[17,50,51],{},"resources"," (data the agent can read), and ",[17,54,55],{},"prompts"," (templates the agent can use). OpenClaw acts as the MCP host, connecting to multiple servers simultaneously. When you ask your agent ",[58,59,60],"em",{},"\"What issues are open in my repo?\"",", OpenClaw routes the request to the GitHub MCP server, which calls the GitHub API, and returns structured data.",[14,63,64,67],{},[17,65,66],{},"Before MCP:"," Every tool needed a custom OpenClaw skill. Each skill was a black box. Security was per-skill. Maintenance was on you.",[14,69,70,73],{},[17,71,72],{},"After MCP:"," One protocol. One configuration format. 1,000+ pre-built servers. Your agent gains capabilities by adding a JSON block to your config, not by writing code.",[14,75,76,79],{},[17,77,78],{},"The shift:"," MCP turns your OpenClaw agent from \"a chatbot that can do a few things\" into \"an agent that can access your entire toolchain.\" The skill ecosystem isn't dead, but for standard tool integrations, MCP is faster, safer, and more maintainable.",[14,81,82],{},[83,84],"img",{"alt":85,"src":86},"Before-vs-after comparison of MCP adoption: three weekends of custom skill writing for GitHub, Notion, and database integration vs 90 seconds of JSON config blocks with 1,000-plus pre-built servers","/img/blog/openclaw-mcp-setup-guide-overview.jpg",[38,88,90],{"id":89},"how-to-set-up-your-first-mcp-server-5-minutes","How to set up your first MCP server (5 minutes)",[14,92,93,96],{},[17,94,95],{},"Step 1:"," Make sure you're on OpenClaw v2026.3+ (MCP support ships natively). Check with:",[98,99,104],"pre",{"className":100,"code":101,"language":102,"meta":103,"style":103},"language-bash shiki shiki-themes github-light","openclaw --version\n","bash","",[105,106,107],"code",{"__ignoreMap":103},[108,109,112,116],"span",{"class":110,"line":111},"line",1,[108,113,115],{"class":114},"s7eDp","openclaw",[108,117,119],{"class":118},"sYu0t"," --version\n",[14,121,122,125,126,129,130,133],{},[17,123,124],{},"Step 2:"," Add the MCP server to your config. Edit ",[105,127,128],{},"~/.openclaw/openclaw.json"," (or use ",[105,131,132],{},"openclaw mcp add","):",[98,135,139],{"className":136,"code":137,"language":138,"meta":103,"style":103},"language-json shiki shiki-themes github-light","{\n  \"mcpServers\": {\n    \"filesystem\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@modelcontextprotocol/server-filesystem\", \"/home/you/Documents\"],\n      \"env\": {}\n    },\n    \"github\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"@modelcontextprotocol/server-github\"],\n      \"env\": {\n        \"GITHUB_PERSONAL_ACCESS_TOKEN\": \"ghp_xxxxxxxxxxxx\"\n      }\n    }\n  }\n}\n","json",[105,140,141,147,156,164,180,206,215,221,229,240,256,263,274,280,286,292],{"__ignoreMap":103},[108,142,143],{"class":110,"line":111},[108,144,146],{"class":145},"sgsFI","{\n",[108,148,150,153],{"class":110,"line":149},2,[108,151,152],{"class":118},"  \"mcpServers\"",[108,154,155],{"class":145},": {\n",[108,157,159,162],{"class":110,"line":158},3,[108,160,161],{"class":118},"    \"filesystem\"",[108,163,155],{"class":145},[108,165,167,170,173,177],{"class":110,"line":166},4,[108,168,169],{"class":118},"      \"command\"",[108,171,172],{"class":145},": ",[108,174,176],{"class":175},"sYBdl","\"npx\"",[108,178,179],{"class":145},",\n",[108,181,183,186,189,192,195,198,200,203],{"class":110,"line":182},5,[108,184,185],{"class":118},"      \"args\"",[108,187,188],{"class":145},": [",[108,190,191],{"class":175},"\"-y\"",[108,193,194],{"class":145},", ",[108,196,197],{"class":175},"\"@modelcontextprotocol/server-filesystem\"",[108,199,194],{"class":145},[108,201,202],{"class":175},"\"/home/you/Documents\"",[108,204,205],{"class":145},"],\n",[108,207,209,212],{"class":110,"line":208},6,[108,210,211],{"class":118},"      \"env\"",[108,213,214],{"class":145},": {}\n",[108,216,218],{"class":110,"line":217},7,[108,219,220],{"class":145},"    },\n",[108,222,224,227],{"class":110,"line":223},8,[108,225,226],{"class":118},"    \"github\"",[108,228,155],{"class":145},[108,230,232,234,236,238],{"class":110,"line":231},9,[108,233,169],{"class":118},[108,235,172],{"class":145},[108,237,176],{"class":175},[108,239,179],{"class":145},[108,241,243,245,247,249,251,254],{"class":110,"line":242},10,[108,244,185],{"class":118},[108,246,188],{"class":145},[108,248,191],{"class":175},[108,250,194],{"class":145},[108,252,253],{"class":175},"\"@modelcontextprotocol/server-github\"",[108,255,205],{"class":145},[108,257,259,261],{"class":110,"line":258},11,[108,260,211],{"class":118},[108,262,155],{"class":145},[108,264,266,269,271],{"class":110,"line":265},12,[108,267,268],{"class":118},"        \"GITHUB_PERSONAL_ACCESS_TOKEN\"",[108,270,172],{"class":145},[108,272,273],{"class":175},"\"ghp_xxxxxxxxxxxx\"\n",[108,275,277],{"class":110,"line":276},13,[108,278,279],{"class":145},"      }\n",[108,281,283],{"class":110,"line":282},14,[108,284,285],{"class":145},"    }\n",[108,287,289],{"class":110,"line":288},15,[108,290,291],{"class":145},"  }\n",[108,293,295],{"class":110,"line":294},16,[108,296,297],{"class":145},"}\n",[14,299,300,301,304,305,308],{},"Add an ",[105,302,303],{},"mcpServers"," block with the server name, command (typically ",[105,306,307],{},"npx","), arguments (the npm package and any config), and environment variables (API tokens).",[14,310,311,314],{},[17,312,313],{},"Step 3:"," Restart your gateway. The server starts automatically as a subprocess. OpenClaw discovers the available tools and makes them available to your agent.",[14,316,317,320,321,324,325,328],{},[17,318,319],{},"Step 4:"," Test it. Ask your agent a question that requires the tool. ",[58,322,323],{},"\"What files are in my Documents folder?\""," (filesystem server). ",[58,326,327],{},"\"What issues are open in openclaw/openclaw?\""," (GitHub server). If the agent uses the tool and returns data, the server is working.",[14,330,331],{},[83,332],{"alt":333,"src":334},"Anatomy of a single openclaw.json mcpServers block: each server is an npm package launched via npx, with the GitHub, Filesystem, and Postgres subprocesses spawned by OpenClaw on gateway startup","/img/blog/openclaw-mcp-setup-guide-config.jpg",[14,336,337,338,343],{},"For the ",[339,340,342],"a",{"href":341},"/blog/openclaw-best-practices","best practices for agent configuration",", our OpenClaw best practices guide covers the broader config patterns that keep MCP servers stable alongside your other OpenClaw settings.",[38,345,347],{"id":346},"the-5-mcp-servers-worth-installing-first","The 5 MCP servers worth installing first",[14,349,350],{},"Out of 1,000+ available servers, here are the five the community installs most often and why.",[352,353,355,356,359],"h3",{"id":354},"_1-filesystem-modelcontextprotocolserver-filesystem","1. Filesystem (",[105,357,358],{},"@modelcontextprotocol/server-filesystem",")",[14,361,362,365],{},[17,363,364],{},"What it does:"," Gives your agent read/write access to specific directories on your machine. List files, read contents, search by name, create files.",[14,367,368,371],{},[17,369,370],{},"Why it's first:"," It's the foundation for every local automation. Your agent can read your notes, write reports, and manage files without browser automation. Scope it to specific directories (never give it root access).",[352,373,375,376,359],{"id":374},"_2-github-modelcontextprotocolserver-github","2. GitHub (",[105,377,378],{},"@modelcontextprotocol/server-github",[14,380,381,383],{},[17,382,364],{}," Read repos, list issues, create PRs, manage branches, search code. Requires a personal access token with appropriate scopes.",[14,385,386,389,390,393,394,393,397,400],{},[17,387,388],{},"Why it matters:"," The most common developer automation. ",[58,391,392],{},"\"Summarize open issues.\""," ",[58,395,396],{},"\"Create a PR from this branch.\"",[58,398,399],{},"\"What changed in the last 3 commits?\""," All work through one server.",[352,402,404,405,408],{"id":403},"_3-postgresql-mysql-sqlite-modelcontextprotocolserver-postgres-etc","3. PostgreSQL / MySQL / SQLite (",[105,406,407],{},"@modelcontextprotocol/server-postgres",", etc.)",[14,410,411,413],{},[17,412,364],{}," Query databases directly. Run SELECT statements, describe schemas, list tables.",[14,415,416,418,419,422],{},[17,417,388],{}," Your agent can answer business questions (",[58,420,421],{},"\"How many users signed up this week?\"",") by querying the database instead of you writing a script. Always configure read-only access unless you explicitly need writes.",[352,424,426,427,359],{"id":425},"_4-slack-modelcontextprotocolserver-slack","4. Slack (",[105,428,429],{},"@modelcontextprotocol/server-slack",[14,431,432,434],{},[17,433,364],{}," Read messages, post messages, manage channels, search conversation history.",[14,436,437,439],{},[17,438,388],{}," Your agent can monitor Slack channels, summarize threads, and post updates without you copy-pasting between Telegram and Slack.",[352,441,443,444,359],{"id":442},"_5-memory-modelcontextprotocolserver-memory","5. Memory (",[105,445,446],{},"@modelcontextprotocol/server-memory",[14,448,449,451],{},[17,450,364],{}," Persistent key-value memory that survives across sessions. The agent can store and retrieve facts without relying on OpenClaw's built-in memory files.",[14,453,454,456,457,460],{},[17,455,388],{}," OpenClaw's ",[105,458,459],{},"MEMORY.md"," has a 3,000-token limit. MCP memory servers don't. They store structured data outside the context window, so your agent remembers without burning tokens.",[14,462,463],{},[83,464],{"alt":465,"src":466},"Ranked card list of the five MCP servers the community installs first — Filesystem, GitHub, PostgreSQL, Slack, Memory — each with its npm package name and the workflow it unlocks","/img/blog/openclaw-mcp-setup-guide-top-5.jpg",[38,468,470],{"id":469},"the-security-problem-nobodys-talking-about-this-matters","The security problem nobody's talking about (this matters)",[14,472,473],{},"Here's what nobody tells you about MCP.",[14,475,476,479],{},[17,477,478],{},"Every MCP server runs as a subprocess with the permissions you give it."," The filesystem server can read every file in the directories you specify. The database server can run every query your credentials allow. The GitHub server can create PRs and modify repos.",[14,481,482,483,487,488,492],{},"The ClawHavoc lesson applies here. When ",[339,484,486],{"href":485},"/blog/clawhub-skills-security-audit","1,400+ malicious skills were found on ClawHub",", the community learned that \"installable code that runs with your agent's permissions\" is an attack surface. MCP servers are the same pattern: code that runs with your credentials, accessed by an AI model that might ",[339,489,491],{"href":490},"/blog/openclaw-agent-hallucination-fix","hallucinate tool calls",".",[14,494,495],{},[17,496,497],{},"Three security rules for MCP:",[499,500,501,508,514],"ol",{},[502,503,504,507],"li",{},[17,505,506],{},"Principle of least privilege."," Give each server the minimum permissions it needs. Read-only database access. Scoped GitHub tokens. Filesystem access limited to specific directories. Never scope wider than necessary.",[502,509,510,513],{},[17,511,512],{},"Audit what the agent calls."," Enable verbose MCP logging so you can see every tool call the agent makes. If your agent is calling the GitHub server to create PRs when you only asked it to read issues, something is wrong.",[502,515,516,519,520,523],{},[17,517,518],{},"Use official servers first."," The ",[105,521,522],{},"@modelcontextprotocol/*"," namespace is maintained by the protocol team. Community servers (the other 900+) vary in quality. Read the source before installing a community server. The ClawHavoc campaign proved that \"it's on a public registry\" doesn't mean \"it's safe.\"",[14,525,337,526,194,530,534],{},[339,527,529],{"href":528},"/blog/openclaw-security-risks","security implications of running third-party code with your agent",[339,531,533],{"href":532},"/blog/openclaw-security-checklist","our OpenClaw security checklist"," covers the broader attack surface.",[14,536,537,540],{},[17,538,539],{},"The MCP security rule:"," MCP servers are as dangerous as the permissions you give them. A filesystem server with root access is a root-access vulnerability. A database server with write permissions is a data-destruction risk. Scope every server tightly. Log every call. Trust official packages first.",[14,542,543,544,548,549,553],{},"If managing MCP server configurations, security scoping, credential injection, subprocess lifecycle, and verbose logging across 5-10 servers sounds like more infrastructure work than building agent workflows, ",[339,545,547],{"href":546},"/openclaw-alternative","BetterClaw handles MCP integrations at the platform level",". Connect tools from the dashboard. Security scoping is built in. Credential management uses ",[339,550,552],{"href":551},"/blog/ai-agent-secrets-auto-purge","secrets auto-purge"," (credentials erased from agent memory after 5 minutes). No subprocess management. No JSON config files. Free tier with 1 agent and BYOK. $19/month per agent for Pro.",[14,555,556],{},[83,557],{"alt":558,"src":559},"Filesystem-server scope-creep example reading .ssh keys and .env credentials when given /home access, plus the three MCP security rules: least privilege, audit tool calls, and prefer official @modelcontextprotocol packages","/img/blog/openclaw-mcp-setup-guide-security.jpg",[38,561,563],{"id":562},"mcp-vs-openclaw-skills-when-to-use-which","MCP vs OpenClaw Skills (when to use which)",[14,565,566],{},"Here's the decision framework the community settled on.",[14,568,569,572],{},[17,570,571],{},"Use MCP when:"," You're connecting to a standard tool that already has an MCP server (GitHub, Slack, databases, file systems, Google Drive, Notion). The server exists. The protocol is standard. Don't reinvent it.",[14,574,575,578],{},[17,576,577],{},"Use OpenClaw Skills when:"," You need custom logic that goes beyond \"call an API and return data.\" Multi-step workflows. Business logic. Custom transformations. Skills can chain multiple operations and maintain internal state. MCP servers are stateless tool providers.",[14,580,581,584],{},[17,582,583],{},"Use both when:"," You need a skill that orchestrates multiple MCP server calls. Example: a \"morning briefing\" skill that queries your database MCP server, reads your GitHub MCP server, checks your Slack MCP server, and compiles a summary.",[14,586,337,587,194,591,594],{},[339,588,590],{"href":589},"/blog/openclaw-plugin-security-clawhub-sha256-verification","verified skills that work alongside MCP",[339,592,593],{"href":485},"our ClawHub skills security audit"," covers how to evaluate which skills are safe to run alongside your MCP servers.",[38,596,598],{"id":597},"the-token-cost-trap-mcp-tools-add-to-your-system-prompt","The token cost trap (MCP tools add to your system prompt)",[14,600,601],{},"But that's not even the real problem.",[14,603,604,607],{},[17,605,606],{},"Every MCP tool definition is added to your system prompt."," Each tool includes its name, description, and input schema. A server with 15 tools adds approximately 1,500-3,000 tokens to your system prompt. Five servers with 15 tools each: 7,500-15,000 tokens of tool definitions on every API call.",[14,609,610,611,615],{},"This is the same bootstrap overhead problem from ",[339,612,614],{"href":613},"/blog/openclaw-agents-md-optimization","the AGENTS.md optimization post",". More tools = more tokens = higher cost on every message, every heartbeat, every tool call.",[14,617,618,621],{},[17,619,620],{},"The fix:"," Only connect the MCP servers you actively use. Don't install 10 servers \"just in case.\" Start with 2-3. Add more when you have specific workflows that need them. Remove servers you haven't used in a week.",[14,623,624,627],{},[17,625,626],{},"BetterClaw's approach:"," Smart context management dynamically loads tool definitions based on the current task, not statically on every call. If the agent isn't doing GitHub work, the GitHub tool definitions don't consume tokens. This is one of the technical differences that makes BetterClaw's context management genuinely different from self-hosted OpenClaw.",[14,629,630],{},[83,631],{"alt":632,"src":633},"Decision framework: use MCP for stateless standard-tool integrations, use OpenClaw Skills for stateful custom workflows, use both when a skill orchestrates multiple MCP servers — with a morning-briefing example","/img/blog/openclaw-mcp-setup-guide-vs-skills.jpg",[38,635,637],{"id":636},"the-bigger-picture-mcp-is-becoming-the-standard","The bigger picture (MCP is becoming the standard)",[14,639,640],{},"Here's the honest take.",[14,642,643,644],{},"MCP is no longer Anthropic's protocol. It's the industry's. In December 2025, it was donated to the Linux Foundation under the Agentic AI Foundation, co-founded by Anthropic, Block, and OpenAI. Claude, ChatGPT, VS Code, Cursor, and OpenClaw all speak MCP. ",[17,645,646],{},"A server built for one agent works with all of them.",[14,648,649,652],{},[17,650,651],{},"The practical implication:"," Every MCP server you set up for OpenClaw also works with Claude Code, Cursor, and any other MCP-compatible tool. You're not building vendor-specific integrations. You're building portable ones.",[14,654,655],{},"This matters because the agent market is still splitting and consolidating. If you invest in ClawHub-specific skills, you're locked to OpenClaw. If you invest in MCP servers, you're portable across every major agent platform. That portability is worth the setup time.",[14,657,658,659,665],{},"If you want MCP integrations without the setup time, subprocess management, and security configuration, ",[339,660,664],{"href":661,"rel":662},"https://app.betterclaw.io/sign-in",[663],"nofollow","give BetterClaw a try",". Free tier with 1 agent and BYOK. $19/month per agent for Pro. MCP server support included. Connect tools from the dashboard. Secrets auto-purge. Smart context management. The protocol is universal. The infrastructure doesn't have to be yours.",[14,667,668],{},[83,669],{"alt":670,"src":671},"System-prompt token breakdown showing AGENTS.md, SOUL.md, MEMORY.md and five MCP servers contributing 7,500-15,000 tokens of tool definitions, with the $112/month Opus overhead and the BetterClaw dynamic-loading workaround","/img/blog/openclaw-mcp-setup-guide-token-cost.jpg",[38,673,675],{"id":674},"frequently-asked-questions","Frequently Asked Questions",[14,677,678],{},[17,679,680],{},"What is MCP (Model Context Protocol) in OpenClaw?",[14,682,683],{},"MCP is an open standard (originally by Anthropic, now under Linux Foundation governance) that lets OpenClaw connect to external tools and data sources through a universal JSON-RPC 2.0 interface. Instead of writing custom skills for each integration, you add an MCP server to your config. There are 1,000+ pre-built servers for GitHub, Slack, databases, file systems, Google Drive, Notion, and more.",[14,685,686],{},[17,687,688],{},"How do MCP servers compare to OpenClaw skills?",[14,690,691],{},"MCP servers are standardized, stateless tool providers (connect to an API, return data). Skills are custom, stateful workflows (multi-step logic, business rules, internal state). Use MCP for standard tool integrations. Use skills for custom business logic. Many advanced setups use both: skills that orchestrate multiple MCP server calls.",[14,693,694],{},[17,695,696],{},"How do I install an MCP server on OpenClaw?",[14,698,699,700,702,703,705,706,708],{},"Add a ",[105,701,303],{}," block to your ",[105,704,128],{}," with the server name, command (",[105,707,307],{},"), npm package, and any required environment variables (API tokens). Restart the gateway. The server starts as a subprocess and OpenClaw discovers the available tools automatically. Test by asking the agent a question that requires the tool. Setup takes about 5 minutes per server.",[14,710,711],{},[17,712,713],{},"How much does MCP add to my OpenClaw token costs?",[14,715,716],{},"Each MCP tool definition adds approximately 100-200 tokens to your system prompt. A server with 15 tools adds 1,500-3,000 tokens. Five servers: 7,500-15,000 tokens of overhead on every API call. At Opus 4.7 pricing ($5/M input), that's $0.037-0.075 per call just in tool definitions. Only connect servers you actively use. BetterClaw's smart context management dynamically loads definitions by task to avoid this overhead.",[14,718,719],{},[17,720,721],{},"Are MCP servers secure enough for production use?",[14,723,724,725,727],{},"With proper configuration, yes. Use official ",[105,726,522],{}," packages first (maintained by the protocol team). Apply least-privilege (read-only database, scoped GitHub tokens, limited filesystem directories). Enable verbose MCP logging. Audit tool calls regularly. Community servers (900+ of the 1,000+) vary in quality. The ClawHavoc campaign showed that public registries are actively targeted. Treat MCP servers with the same caution as ClawHub skills.",[38,729,731],{"id":730},"related-reading","Related Reading",[733,734,735,741,747,753,759,765],"ul",{},[502,736,737,740],{},[339,738,739],{"href":341},"OpenClaw Best Practices"," — Config patterns that keep MCP servers stable alongside the rest of your setup",[502,742,743,746],{},[339,744,745],{"href":485},"ClawHub Skills Security Audit"," — Lessons from the 1,400+ malicious-skill campaign that apply to MCP servers too",[502,748,749,752],{},[339,750,751],{"href":532},"OpenClaw Security Checklist"," — Least-privilege patterns, credential scoping, audit logging",[502,754,755,758],{},[339,756,757],{"href":613},"Stop Making Your OpenClaw Agent Re-Read Files"," — Same token-overhead math applies to MCP tool definitions",[502,760,761,764],{},[339,762,763],{"href":551},"AI Agent Secrets Auto-Purge"," — Credential lifecycle for agents that hold tokens for many tools",[502,766,767,770],{},[339,768,769],{"href":490},"OpenClaw Agent Hallucinating? 5 Fixes That Actually Work"," — Why an agent with MCP access can still call the wrong tool with invented parameters",[772,773,774],"style",{},"html pre.shiki code .s7eDp, html code.shiki .s7eDp{--shiki-default:#6F42C1}html pre.shiki code .sYu0t, html code.shiki .sYu0t{--shiki-default:#005CC5}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html pre.shiki code .sgsFI, html code.shiki .sgsFI{--shiki-default:#24292E}html pre.shiki code .sYBdl, html code.shiki .sYBdl{--shiki-default:#032F62}",{"title":103,"searchDepth":149,"depth":149,"links":776},[777,778,779,791,792,793,794,795,796],{"id":40,"depth":149,"text":41},{"id":89,"depth":149,"text":90},{"id":346,"depth":149,"text":347,"children":780},[781,783,785,787,789],{"id":354,"depth":158,"text":782},"1. Filesystem (@modelcontextprotocol/server-filesystem)",{"id":374,"depth":158,"text":784},"2. GitHub (@modelcontextprotocol/server-github)",{"id":403,"depth":158,"text":786},"3. PostgreSQL / MySQL / SQLite (@modelcontextprotocol/server-postgres, etc.)",{"id":425,"depth":158,"text":788},"4. Slack (@modelcontextprotocol/server-slack)",{"id":442,"depth":158,"text":790},"5. Memory (@modelcontextprotocol/server-memory)",{"id":469,"depth":149,"text":470},{"id":562,"depth":149,"text":563},{"id":597,"depth":149,"text":598},{"id":636,"depth":149,"text":637},{"id":674,"depth":149,"text":675},{"id":730,"depth":149,"text":731},"Setup Guides","2026-05-14","Set up MCP on OpenClaw in 5 minutes. Connect GitHub, Slack, databases, and 1,000+ tools. Here are the 5 servers to install first and the security trap to avoid.","md",false,"/img/blog/openclaw-mcp-setup-guide.jpg",null,{},true,"/blog/openclaw-mcp-setup-guide","11 min read",{"title":5,"description":799},"OpenClaw MCP Setup: Connect 1,000+ Tools (2026)","blog/openclaw-mcp-setup-guide",[812,813,814,815,816,817,818,819,820,821],"OpenClaw MCP","Model Context Protocol OpenClaw","MCP server setup","OpenClaw MCP guide","MCP tools OpenClaw","OpenClaw integrations","MCP security","OpenClaw GitHub MCP","OpenClaw filesystem MCP","MCP vs skills","8XVorqA3faadcZVO2uE2O6xWbvZyPhmNVsEIiK3bNvw",[824,1235],{"id":825,"title":826,"author":827,"body":828,"category":797,"date":1217,"description":1218,"extension":800,"featured":801,"image":1219,"imageHeight":803,"imageWidth":803,"meta":1220,"navigation":805,"path":1221,"readingTime":1222,"seo":1223,"seoTitle":1224,"stem":1225,"tags":1226,"updatedDate":1217,"__hash__":1234},"blog/blog/openclaw-git-clone.md","OpenClaw Git Clone: How to Install from Source (and When You Shouldn't)",{"name":7,"role":8,"avatar":9},{"type":11,"value":829,"toc":1202},[830,835,838,841,844,848,851,861,871,877,883,889,893,896,906,916,925,934,943,950,957,963,967,970,985,997,1010,1019,1025,1029,1032,1038,1047,1053,1059,1063,1066,1073,1076,1079,1090,1096,1100,1103,1106,1113,1116,1123,1125,1129,1148,1152,1158,1162,1171,1175,1190,1194],[14,831,832],{},[58,833,834],{},"The full guide to building OpenClaw from the GitHub repo. Plus the honest answer about whether you actually need to.",[14,836,837],{},"I cloned the OpenClaw repo for the first time because I wanted to understand what the gateway actually does under the hood. The TypeScript source. The plugin system. The channel routing. I wanted to read the code before I trusted it with my API keys.",[14,839,840],{},"Two hours later, I had a working dev build. Three days later, I'd read enough of the codebase to understand why certain design decisions were made and where the security surface lives. That understanding has shaped everything we've built at BetterClaw since.",[14,842,843],{},"If you're a developer who wants to build OpenClaw from source, whether to contribute, debug, customize, or just learn, this is the guide. It covers the git clone, the build process, the common failures, and the honest assessment of when building from source makes sense versus when it doesn't.",[38,845,847],{"id":846},"prerequisites-check-these-before-you-clone","Prerequisites (check these before you clone)",[14,849,850],{},"OpenClaw's source build requires specific tooling. Missing any of these means a failed build and a frustrating hour of debugging dependency errors.",[14,852,853,856,857,860],{},[17,854,855],{},"Node.js 24 (recommended) or Node.js 22.16+."," Older Node versions will fail. Check with ",[105,858,859],{},"node --version",". If you're on Node 20 or below, upgrade before touching anything.",[14,862,863,866,867,870],{},[17,864,865],{},"pnpm"," as the package manager. OpenClaw's monorepo uses pnpm workspaces. npm and yarn won't resolve dependencies correctly. Install with ",[105,868,869],{},"npm install -g pnpm"," if you don't have it.",[14,872,873,876],{},[17,874,875],{},"Git"," (obviously). You need git to clone the repo. If you're reading an article about git clone and don't have git installed, we should talk.",[14,878,879,882],{},[17,880,881],{},"Bun"," (optional). Bun can run TypeScript directly and is useful for certain development workflows, but it's not required for the standard build.",[14,884,885],{},[83,886],{"alt":887,"src":888},"Prerequisites for an OpenClaw source build: Node.js 22.16+, pnpm, and Git","/img/blog/openclaw-git-clone-prerequisites.jpg",[38,890,892],{"id":891},"the-git-clone-and-build-process","The git clone and build process",[14,894,895],{},"The OpenClaw source build follows a standard monorepo pattern. Clone, install dependencies, run setup, start the dev server.",[14,897,898,901,902,905],{},[17,899,900],{},"Step 1: Clone the repository."," The OpenClaw git clone pulls approximately 430,000 lines of code from the main repository at ",[105,903,904],{},"github.com/openclaw/openclaw",". The repo includes the gateway, all bundled plugins, the Control UI, documentation, and test infrastructure.",[14,907,908,911,912,915],{},[17,909,910],{},"Step 2: Install dependencies with pnpm."," Run ",[105,913,914],{},"pnpm install"," from the project root. This resolves all workspace dependencies across the monorepo. First install takes 2-5 minutes depending on your network speed.",[14,917,918,393,921,924],{},[17,919,920],{},"Step 3: Run the setup wizard.",[105,922,923],{},"pnpm openclaw setup"," walks you through configuring your workspace, gateway settings, channel connections, and initial skill selection. This is the same setup wizard that the npm package uses, but running against your local source build.",[14,926,927,911,930,933],{},[17,928,929],{},"Step 4: (Optional) Build the Control UI.",[105,931,932],{},"pnpm ui:build"," to pre-build the web-based control interface. This isn't required for headless operation but is useful if you want the browser dashboard.",[14,935,936,393,939,942],{},[17,937,938],{},"Step 5: Start the development gateway.",[105,940,941],{},"pnpm gateway:watch"," starts the gateway with auto-reload on source and config changes. Every time you edit a file, the gateway restarts with your changes. This is the core development loop.",[14,944,337,945,949],{},[339,946,948],{"href":947},"/blog/openclaw-setup-guide-complete","complete setup guide including non-source installation",", our setup post covers the npm install path that most users should start with.",[14,951,952,953,956],{},"The source build gives you auto-reload on file changes, which is essential for development. If you're not modifying the source code, the npm global install (",[105,954,955],{},"npm install -g openclaw@latest",") is simpler and produces the same runtime.",[14,958,959],{},[83,960],{"alt":961,"src":962},"The 5-step source build flow: clone → install → setup → build UI → watch gateway","/img/blog/openclaw-git-clone-build-steps.jpg",[38,964,966],{"id":965},"where-the-git-clone-build-breaks-and-the-fixes","Where the git clone build breaks (and the fixes)",[14,968,969],{},"Here's where most people get it wrong.",[14,971,972,977,978,981,982,984],{},[17,973,974,976],{},[105,975,914],{}," fails with peer dependency errors."," This usually means your Node version is too old. OpenClaw requires Node 24 (recommended) or 22.16+. The fix: upgrade Node, delete ",[105,979,980],{},"node_modules"," and the pnpm lock file, run ",[105,983,914],{}," again.",[14,986,987,992,993,996],{},[17,988,989,991],{},[105,990,923],{}," writes config to the wrong location."," The setup wizard writes to ",[105,994,995],{},"~/.openclaw/workspace"," by default. If you're running multiple OpenClaw instances or working with a forked config, verify the output path. The setup wizard is safe to re-run if you need to change settings.",[14,998,999,1004,1005,1009],{},[17,1000,1001,1003],{},[105,1002,941],{}," crashes on startup with plugin errors."," After the 2026.4.7 release, plugin loading changed to use manifest-declared activation. If you cloned an older branch and merged upstream changes, some plugin configs may be incompatible. Check the release notes for plugin migration steps. For the ",[339,1006,1008],{"href":1007},"/blog/openclaw-2026-4-7-update","2026.4.7 update details including what breaks",", our update guide covers the specific plugin changes.",[14,1011,1012,1015,1016,1018],{},[17,1013,1014],{},"The Control UI build fails on low-memory systems."," The UI build is memory-intensive. Systems with less than 4GB RAM may fail during the webpack build step. The fix: increase swap space, or skip the UI build (",[105,1017,932],{},") and use the gateway in headless mode.",[14,1020,1021],{},[83,1022],{"alt":1023,"src":1024},"Common OpenClaw source-build failures and the fixes that actually work","/img/blog/openclaw-git-clone-failures.jpg",[38,1026,1028],{"id":1027},"what-building-from-source-actually-gives-you","What building from source actually gives you",[14,1030,1031],{},"The OpenClaw git clone gives you three things the npm install doesn't.",[14,1033,1034,1037],{},[17,1035,1036],{},"Source-level debugging."," You can set breakpoints in the gateway code, step through plugin initialization, and trace exactly how a message flows from your Telegram bot through the gateway to the model provider and back. This is invaluable for understanding agent behavior at the framework level.",[14,1039,1040,1043,1044,1046],{},[17,1041,1042],{},"Contribution workflow."," If you want to contribute to OpenClaw (850+ contributors, 7,900+ open issues), you need a source build. Fork the repo, clone your fork, create a branch, make changes, run ",[105,1045,941],{}," to test, submit a PR.",[14,1048,1049,1052],{},[17,1050,1051],{},"Custom builds."," If you need to modify core gateway behavior (custom routing logic, non-standard channel handling, internal plugins that shouldn't be published), the source build lets you make framework-level changes that the npm package can't.",[14,1054,1055],{},[83,1056],{"alt":1057,"src":1058},"What the source build unlocks: debugging, contribution workflow, and custom gateway builds","/img/blog/openclaw-git-clone-benefits.jpg",[38,1060,1062],{"id":1061},"when-building-from-source-is-the-wrong-approach","When building from source is the wrong approach",[14,1064,1065],{},"Here's what nobody tells you about the OpenClaw git clone.",[14,1067,1068,1069,1072],{},"If you just want to run an agent, the source build is overkill. The npm global install (",[105,1070,1071],{},"openclaw onboard --install-daemon",") gives you the same runtime, the same features, and the same performance. It also installs the system daemon so the gateway runs automatically in the background. The source build doesn't do this. You manage the process yourself.",[14,1074,1075],{},"If you want to configure an agent, you don't need the source. SOUL.md, model selection, skill installation, channel connections, memory configuration. All of this works identically on the npm install. You don't need 430,000 lines of source code to write a SOUL.md.",[14,1077,1078],{},"If you want to avoid infrastructure management entirely, building from source is the opposite of what you want. The source build gives you more infrastructure to manage, not less.",[14,1080,1081,1082,1085,1086,492],{},"If you're evaluating OpenClaw and realized you'd rather configure your agent than compile its source code, ",[339,1083,1084],{"href":546},"BetterClaw eliminates the build and infrastructure entirely",". Free tier with 1 agent and BYOK. $29/month per agent for Pro. 60-second deploy. Smart context management, verified skills, secrets auto-purge. The platform handles the 430,000 lines of code so you handle the ",[339,1087,1089],{"href":1088},"/blog/openclaw-soulmd-guide","SOUL.md",[14,1091,1092],{},[83,1093],{"alt":1094,"src":1095},"BetterClaw skips the 15–30 minute source build: sign in and deploy in under a minute","/img/blog/openclaw-git-clone-betterclaw.jpg",[38,1097,1099],{"id":1098},"the-honest-recommendation","The honest recommendation",[14,1101,1102],{},"The OpenClaw git clone makes sense for three types of developers: contributors who want to submit PRs, developers who need source-level debugging to diagnose framework behavior, and builders who need custom gateway modifications.",[14,1104,1105],{},"For everyone else, the npm install is the right starting point. It produces the same runtime, supports the same features, and requires significantly less tooling.",[14,1107,337,1108,1112],{},[339,1109,1111],{"href":1110},"/blog/openclaw-self-hosting-vs-managed","broader decision of whether to self-host at all",", our comparison covers the ten scenarios where self-hosting makes sense and the ten where it doesn't.",[14,1114,1115],{},"The source build isn't the hard part. The hard part is everything that comes after: gateway security, skill supply chain risk (1,400+ malicious skills on ClawHub), credential protection, update management, and the ongoing time cost of maintaining a production agent. The git clone takes 30 seconds. The infrastructure management takes indefinitely.",[14,1117,1118,1119,1122],{},"If you want the agent without the infrastructure, ",[339,1120,664],{"href":661,"rel":1121},[663],". Free tier with 1 agent and BYOK. $19/month per agent for Pro (up to 25 agents, each billed at $19/month) with full access. 60-second deploy. Verified skills. Secrets auto-purge. Smart context management. We handle the 430,000 lines of TypeScript. You handle the interesting part: what your agent actually does.",[38,1124,675],{"id":674},[352,1126,1128],{"id":1127},"how-do-i-install-openclaw-from-source-using-git-clone","How do I install OpenClaw from source using git clone?",[14,1130,1131,1132,1135,1136,1138,1139,1141,1142,1144,1145,1147],{},"Clone the repo with ",[105,1133,1134],{},"git clone"," from ",[105,1137,904],{},", then run ",[105,1140,914],{}," for dependencies, ",[105,1143,923],{}," for configuration, and ",[105,1146,941],{}," to start the development server. Prerequisites: Node.js 24 (or 22.16+) and pnpm. The full process takes 15-30 minutes including the first dependency install.",[352,1149,1151],{"id":1150},"whats-the-difference-between-git-clone-and-npm-install-for-openclaw","What's the difference between git clone and npm install for OpenClaw?",[14,1153,1154,1155,1157],{},"The npm global install (",[105,1156,955],{},") gives you the compiled runtime ready to use. The git clone gives you the full 430,000-line source codebase with auto-reload development mode, source-level debugging, and the ability to modify framework code. Both produce the same runtime agent. The source build is for developers contributing to the project or building custom modifications. The npm install is for everyone else.",[352,1159,1161],{"id":1160},"what-nodejs-version-does-openclaw-require","What Node.js version does OpenClaw require?",[14,1163,1164,1165,1167,1168,1170],{},"Node.js 24 (recommended) or Node.js 22.16+. Older versions (Node 20 and below) will fail during ",[105,1166,914],{}," with peer dependency errors. Check with ",[105,1169,859],{}," before cloning. If you need to upgrade, use nvm (Node Version Manager) or download directly from nodejs.org.",[352,1172,1174],{"id":1173},"how-long-does-an-openclaw-source-build-take","How long does an OpenClaw source build take?",[14,1176,1177,1178,1180,1181,1183,1184,1186,1187,1189],{},"The git clone itself takes 30-60 seconds. ",[105,1179,914],{}," takes 2-5 minutes on first run. ",[105,1182,923],{}," takes 5-10 minutes (interactive). ",[105,1185,932],{}," takes 2-5 minutes for the Control UI. Total: approximately 15-30 minutes for a complete source build. Subsequent builds after code changes are near-instant due to ",[105,1188,941],{}," auto-reload.",[352,1191,1193],{"id":1192},"should-i-build-openclaw-from-source-or-use-betterclaw","Should I build OpenClaw from source or use BetterClaw?",[14,1195,1196,1197,1201],{},"Build from source if you want to contribute to the OpenClaw project, need source-level debugging, or require custom gateway modifications. Use ",[339,1198,1200],{"href":1199},"/","BetterClaw"," if you want a working agent without managing infrastructure. BetterClaw deploys in 60 seconds versus the source build's 15-30 minutes, includes verified skills (eliminates ClawHub supply chain risk), secrets auto-purge, and smart context management. Free tier with 1 agent and BYOK. $29/month for Pro.",{"title":103,"searchDepth":149,"depth":149,"links":1203},[1204,1205,1206,1207,1208,1209,1210],{"id":846,"depth":149,"text":847},{"id":891,"depth":149,"text":892},{"id":965,"depth":149,"text":966},{"id":1027,"depth":149,"text":1028},{"id":1061,"depth":149,"text":1062},{"id":1098,"depth":149,"text":1099},{"id":674,"depth":149,"text":675,"children":1211},[1212,1213,1214,1215,1216],{"id":1127,"depth":158,"text":1128},{"id":1150,"depth":158,"text":1151},{"id":1160,"depth":158,"text":1161},{"id":1173,"depth":158,"text":1174},{"id":1192,"depth":158,"text":1193},"2026-04-23","Build OpenClaw from source: git clone, pnpm install, common build failures, and when you should use npm install or a managed platform instead.","/img/blog/openclaw-git-clone.jpg",{},"/blog/openclaw-git-clone","9 min read",{"title":826,"description":1218},"OpenClaw Git Clone: Source Install Guide (2026)","blog/openclaw-git-clone",[1227,1228,1229,1230,1231,1232,1233],"OpenClaw git clone","OpenClaw source install","OpenClaw GitHub build","OpenClaw from source","OpenClaw pnpm install","OpenClaw development setup","build OpenClaw","cDG8PKTqb8DO51Gf-MAHrltgdjRL_UMYRIYiOZ-HdA4",{"id":1236,"title":1237,"author":1238,"body":1239,"category":797,"date":1645,"description":1646,"extension":800,"featured":801,"image":1647,"imageHeight":803,"imageWidth":803,"meta":1648,"navigation":805,"path":1649,"readingTime":1650,"seo":1651,"seoTitle":1652,"stem":1653,"tags":1654,"updatedDate":1645,"__hash__":1661},"blog/blog/openclaw-telegram-setup.md","How to Connect OpenClaw to Telegram (It's Easier Than You Think)",{"name":7,"role":8,"avatar":9},{"type":11,"value":1240,"toc":1623},[1241,1246,1249,1252,1255,1259,1262,1268,1274,1280,1286,1292,1296,1299,1305,1323,1329,1340,1346,1354,1358,1361,1365,1368,1374,1378,1381,1386,1390,1393,1398,1409,1415,1419,1422,1425,1431,1437,1443,1447,1450,1454,1461,1464,1467,1476,1486,1492,1496,1499,1505,1511,1517,1520,1533,1539,1543,1546,1554,1557,1560,1563,1573,1576,1580,1583,1587,1598,1602,1605,1609,1612,1616],[14,1242,1243],{},[17,1244,1245],{},"Most guides make this look complicated. It's not. Here's the native connection that takes 2 minutes and the dedicated bot setup for when you need more.",[14,1247,1248],{},"Most guides about OpenClaw Telegram setup start with BotFather tokens, webhook URLs, and config file edits. You read three paragraphs and think this is going to take all afternoon.",[14,1250,1251],{},"It doesn't. OpenClaw connects to Telegram natively through the chat interface. No bot tokens. No webhook configuration. For 90% of users, the native connection is all you need, and it takes about two minutes.",[14,1253,1254],{},"Here's how.",[38,1256,1258],{"id":1257},"the-native-connection-start-here","The native connection (start here)",[14,1260,1261],{},"This is the OpenClaw Telegram setup that most people actually need. It connects your personal Telegram account directly to your OpenClaw agent. You message the agent like you'd message a friend. The agent responds in the same chat.",[14,1263,1264,1267],{},[17,1265,1266],{},"Step 1: Open the OpenClaw chat interface."," This is either the web UI (if you're running the gateway locally or on a VPS) or the terminal-based chat. You need the agent running and responsive before connecting any channels.",[14,1269,1270,1273],{},[17,1271,1272],{},"Step 2: Start the Telegram connection from OpenClaw."," In the chat interface, use the channel connection flow. OpenClaw will generate a connection link or QR code for Telegram. This is the native pairing process that connects your Telegram account to the agent through the gateway.",[14,1275,1276,1279],{},[17,1277,1278],{},"Step 3: Authenticate in Telegram."," Click the link or scan the code from your Telegram app. Authorize the connection. You'll see a confirmation in both Telegram and the OpenClaw interface.",[14,1281,1282,1285],{},[17,1283,1284],{},"Step 4: Send a test message."," Open Telegram and send \"hello\" to the agent chat. If you get a response, you're connected. The whole process takes about two minutes.",[14,1287,1288],{},[83,1289],{"alt":1290,"src":1291},"OpenClaw Telegram native connection flow","/img/blog/openclaw-telegram-native-connection.jpg",[38,1293,1295],{"id":1294},"what-you-can-do-once-its-connected","What you can do once it's connected",[14,1297,1298],{},"Once your OpenClaw Telegram setup is complete, the agent works through Telegram just like it works through the web interface. Everything carries over.",[14,1300,1301,1304],{},[17,1302,1303],{},"Send messages and get responses."," Type naturally. Ask questions. Give instructions. The agent responds in the same chat thread. You can send voice notes too, and the agent will process the audio and respond in text.",[14,1306,1307,1310,1311,1314,1315,1318,1319,1322],{},[17,1308,1309],{},"All OpenClaw commands work."," The slash commands you use in the web interface (like ",[105,1312,1313],{},"/model"," to switch models, ",[105,1316,1317],{},"/memory"," to check what the agent remembers, ",[105,1320,1321],{},"/status"," for health checks) work identically in Telegram. Type them in the chat and the agent processes them.",[14,1324,1325,1328],{},[17,1326,1327],{},"Memory persists across platforms."," If you started a conversation on the web interface and switch to Telegram, the agent remembers the context. Your preferences, your ongoing projects, your previous requests. It's the same agent, just accessible from a different app.",[14,1330,1331,1334,1335,1339],{},[17,1332,1333],{},"Skills work normally."," Web search, calendar checks, file operations, browser automation. Whatever ",[339,1336,1338],{"href":1337},"/blog/best-openclaw-skills","skills your agent has installed"," work through Telegram the same way they work through any other channel. The agent receives your message via Telegram, processes it through the same skill and model pipeline, and sends the response back to Telegram.",[14,1341,1342,1345],{},[17,1343,1344],{},"Cron jobs deliver to Telegram."," This is where Telegram gets really useful. Set up a morning briefing cron job and the agent sends your daily summary directly to your Telegram chat at 7 AM. No need to open a browser or check a dashboard. The information comes to you.",[14,1347,1348,1349,1353],{},"For a broader look at what OpenClaw agents can actually do across all channels, our ",[339,1350,1352],{"href":1351},"/blog/best-openclaw-use-cases","use cases guide"," covers the workflows that provide the most value.",[38,1355,1357],{"id":1356},"when-things-dont-connect","When things don't connect",[14,1359,1360],{},"Three issues account for almost every failed OpenClaw Telegram setup.",[352,1362,1364],{"id":1363},"the-gateway-isnt-running","The gateway isn't running",[14,1366,1367],{},"If your OpenClaw gateway isn't actively running when you try to connect Telegram, the connection will fail silently. There's no helpful error message. The link or QR code just doesn't work.",[14,1369,1370,1373],{},[17,1371,1372],{},"Fix:"," Make sure the gateway is running and responsive before starting the Telegram connection. Send a test message in the web interface first. If that works, the gateway is up.",[352,1375,1377],{"id":1376},"network-connectivity-issues","Network connectivity issues",[14,1379,1380],{},"If your OpenClaw instance can't reach Telegram's servers (firewall blocking outbound connections, DNS issues, VPN interference), the connection fails.",[14,1382,1383,1385],{},[17,1384,1372],{}," Test whether your server can reach Telegram's API endpoint. If you're behind a corporate VPN or a restrictive firewall, you may need to whitelist Telegram's IP ranges or route the traffic differently.",[352,1387,1389],{"id":1388},"authentication-timeout","Authentication timeout",[14,1391,1392],{},"The connection link or QR code expires after a short window. If you take too long to authenticate in Telegram, it times out.",[14,1394,1395,1397],{},[17,1396,1372],{}," Start the connection process and immediately switch to Telegram to complete the authentication. Don't read three paragraphs of documentation between generating the link and clicking it.",[14,1399,1400,1401,1404,1405,1408],{},"For the broader ",[339,1402,1403],{"href":947},"OpenClaw troubleshooting guide covering all common setup errors",", our ",[339,1406,1407],{"href":947},"setup walkthrough"," covers the full installation sequence and where things typically break.",[14,1410,1411],{},[83,1412],{"alt":1413,"src":1414},"OpenClaw Telegram troubleshooting errors","/img/blog/openclaw-telegram-troubleshooting.jpg",[38,1416,1418],{"id":1417},"do-you-need-a-dedicated-telegram-bot-instead","Do you need a dedicated Telegram bot instead?",[14,1420,1421],{},"Most readers can skip this section. The native connection handles personal use perfectly.",[14,1423,1424],{},"But if you need any of the following, a dedicated Telegram bot is the way to go.",[14,1426,1427,1430],{},[17,1428,1429],{},"Multiple people need to message the same agent."," The native connection links your personal Telegram account to the agent. If your team or customers also need to message the agent, they need a bot with its own username that anyone can find and message.",[14,1432,1433,1436],{},[17,1434,1435],{},"You want a custom bot identity."," A dedicated bot has its own name, profile picture, and username. Instead of messaging your personal account, people message @YourCompanyBot. This matters for customer-facing use cases.",[14,1438,1439,1442],{},[17,1440,1441],{},"You need the agent accessible in group chats."," Native connections work in direct messages. If you want your agent responding in a Telegram group or forum topic, you need a dedicated bot that can be added as a group member.",[352,1444,1446],{"id":1445},"what-a-dedicated-bot-gives-you","What a dedicated bot gives you",[14,1448,1449],{},"A bot with its own Telegram username means anyone can message it without knowing your personal account. It can be added to groups. It has its own profile. It shows up as a separate entity in Telegram search. For customer support, team assistants, or public-facing agents, this is necessary.",[352,1451,1453],{"id":1452},"the-botfather-setup-condensed-version","The BotFather setup (condensed version)",[14,1455,1456,1457,1460],{},"Open Telegram and search for @BotFather. Start a chat and send the ",[105,1458,1459],{},"/newbot"," command. BotFather will ask for a display name and a username (must end in \"bot\"). Once created, BotFather gives you an API token.",[14,1462,1463],{},"Copy that token into your OpenClaw config under the Telegram provider section. Set the token as the credential for the Telegram channel. Restart the gateway.",[14,1465,1466],{},"Your bot should now appear in Telegram search. Message it and you should get a response from your OpenClaw agent.",[14,1468,1469,1470,1475],{},"For the full details on bot permissions, privacy mode, and group settings, ",[339,1471,1474],{"href":1472,"rel":1473},"https://core.telegram.org/bots/api",[663],"Telegram's official Bot API documentation"," covers everything. The setup above gets you a working bot. The docs handle the edge cases.",[14,1477,1478,1481,1482,1485],{},[17,1479,1480],{},"Native connection = personal use."," Takes 2 minutes. No bot needed. ",[17,1483,1484],{},"Dedicated bot = team or customer use."," Takes 10 minutes. Needs BotFather.",[14,1487,1488],{},[83,1489],{"alt":1490,"src":1491},"OpenClaw Telegram native vs dedicated bot","/img/blog/openclaw-telegram-native-vs-bot.jpg",[38,1493,1495],{"id":1494},"native-connection-vs-dedicated-bot-which-one","Native connection vs dedicated bot: which one?",[14,1497,1498],{},"This comes down to three questions.",[14,1500,1501,1504],{},[17,1502,1503],{},"Is this just for you?"," Native connection. It's faster, simpler, and you don't need a bot username cluttering your setup.",[14,1506,1507,1510],{},[17,1508,1509],{},"Do other people need to message the agent?"," Dedicated bot. Your team members, customers, or anyone else needs a bot they can find and message independently.",[14,1512,1513,1516],{},[17,1514,1515],{},"Do you need the agent in group chats?"," Dedicated bot. Native connections don't work in groups. Bots do.",[14,1518,1519],{},"If you answered \"just me\" to all three, use the native connection. If any answer is \"yes,\" set up a dedicated bot. You can always start with the native connection and add a bot later when you need it.",[14,1521,1522,1523,1527,1528,1532],{},"If you want to connect the same agent across Telegram, WhatsApp, Slack, Discord, and other platforms simultaneously, the ",[339,1524,1526],{"href":1525},"/compare/openclaw","managed vs self-hosted comparison"," covers how multi-channel support works on different deployment options. On a self-hosted setup, each channel requires its own configuration. On ",[339,1529,1531],{"href":1530},"/openclaw-hosting","Better Claw",", Telegram and 14 other platforms are available from the dashboard with zero manual setup. $19/month per agent, BYOK.",[14,1534,1535],{},[83,1536],{"alt":1537,"src":1538},"OpenClaw Telegram vs multi-channel comparison","/img/blog/openclaw-telegram-multichannel-comparison.jpg",[38,1540,1542],{"id":1541},"the-part-most-telegram-guides-skip","The part most Telegram guides skip",[14,1544,1545],{},"Here's what nobody tells you about running your agent on Telegram long-term.",[14,1547,1548,1549,1553],{},"Telegram is probably the most popular platform for OpenClaw agents. The community favors it because it's fast, has good bot support, works globally, and the notification system is reliable. Most OpenClaw tutorials (including ",[339,1550,1552],{"href":1551},"/blog/networkchuck-openclaw-tutorial","NetworkChuck's popular 32-minute setup video",") use Telegram as the primary demo platform.",[14,1555,1556],{},"But Telegram is also the platform where most people stop. They connect Telegram and never add a second channel. That's fine for personal use. For anything customer-facing, you're limiting yourself to users who have Telegram installed.",[14,1558,1559],{},"WhatsApp has 2.7 billion monthly active users. Slack is where most teams already communicate. Discord is where many communities live. Connecting just Telegram is like opening a store on one street and ignoring every other street in town.",[14,1561,1562],{},"The agent doesn't care which platform delivers the message. It processes the same way regardless of channel. Adding a second or third platform doesn't add complexity to the agent itself. It just adds configuration work on the hosting side.",[14,1564,1565,1566,1568,1569,492],{},"If you're on ",[339,1567,1200],{"href":1530},", Telegram is available as a pre-configured channel from your dashboard, along with 14 other platforms, ",[339,1570,1572],{"href":661,"rel":1571},[663],"no setup steps required",[38,1574,1575],{"id":674},"Frequently asked questions",[352,1577,1579],{"id":1578},"how-do-i-set-up-openclaw-with-telegram","How do I set up OpenClaw with Telegram?",[14,1581,1582],{},"The fastest method is the native connection through the OpenClaw chat interface. Open the OpenClaw UI, start the Telegram connection flow, authenticate in your Telegram app, and send a test message. The whole process takes about 2 minutes. No BotFather tokens or webhook configuration needed for personal use. For team or customer-facing use, create a dedicated bot through @BotFather and add the token to your OpenClaw config.",[352,1584,1586],{"id":1585},"how-does-connecting-openclaw-to-telegram-compare-to-other-platforms","How does connecting OpenClaw to Telegram compare to other platforms?",[14,1588,1589,1590,1594,1595,1597],{},"Telegram is the easiest platform to connect and the most commonly used in the OpenClaw community. ",[339,1591,1593],{"href":1592},"/blog/openclaw-whatsapp-setup","WhatsApp"," requires additional business API configuration. Discord needs a bot application setup. Slack needs an app installation. Telegram's native connection is the simplest, which is why most tutorials start with it. On managed platforms like ",[339,1596,1200],{"href":1530},", all channels are preconfigured and require no manual setup.",[352,1599,1601],{"id":1600},"how-long-does-the-openclaw-telegram-setup-take","How long does the OpenClaw Telegram setup take?",[14,1603,1604],{},"Native connection: about 2 minutes. Dedicated bot through BotFather: about 10 minutes. The native connection is ideal for personal use (just you messaging the agent). The dedicated bot is needed for team access, customer-facing bots, or group chat usage. Start with the native connection and add a dedicated bot later if your needs expand.",[352,1606,1608],{"id":1607},"does-connecting-openclaw-to-telegram-cost-anything-extra","Does connecting OpenClaw to Telegram cost anything extra?",[14,1610,1611],{},"No. Telegram connections are free. The cost of running an OpenClaw agent comes from the hosting ($12–29/month depending on self-hosted VPS or managed platform) and the AI model API costs ($5–30/month depending on model and usage). Telegram itself adds zero cost. The same applies to all 15+ channels OpenClaw supports.",[352,1613,1615],{"id":1614},"is-it-safe-to-connect-openclaw-to-my-personal-telegram","Is it safe to connect OpenClaw to my personal Telegram?",[14,1617,1618,1619,1622],{},"The native connection links your personal Telegram to the agent, meaning the agent can receive and respond to messages through your account context. For personal use, this is safe as long as your OpenClaw instance is properly secured (gateway bound to loopback, ",[339,1620,1621],{"href":532},"skills vetted",", spending caps set). For anything customer-facing, use a dedicated bot instead of your personal account. This keeps your personal messages separate from agent interactions.",{"title":103,"searchDepth":149,"depth":149,"links":1624},[1625,1626,1627,1632,1636,1637,1638],{"id":1257,"depth":149,"text":1258},{"id":1294,"depth":149,"text":1295},{"id":1356,"depth":149,"text":1357,"children":1628},[1629,1630,1631],{"id":1363,"depth":158,"text":1364},{"id":1376,"depth":158,"text":1377},{"id":1388,"depth":158,"text":1389},{"id":1417,"depth":149,"text":1418,"children":1633},[1634,1635],{"id":1445,"depth":158,"text":1446},{"id":1452,"depth":158,"text":1453},{"id":1494,"depth":149,"text":1495},{"id":1541,"depth":149,"text":1542},{"id":674,"depth":149,"text":1575,"children":1639},[1640,1641,1642,1643,1644],{"id":1578,"depth":158,"text":1579},{"id":1585,"depth":158,"text":1586},{"id":1600,"depth":158,"text":1601},{"id":1607,"depth":158,"text":1608},{"id":1614,"depth":158,"text":1615},"2026-04-01","OpenClaw connects to Telegram natively in 2 minutes. No BotFather needed for personal use. Here's the setup plus when you actually need a dedicated bot.","/img/blog/openclaw-telegram-setup.jpg",{},"/blog/openclaw-telegram-setup","8 min read",{"title":1237,"description":1646},"OpenClaw Telegram Setup: Connect in 2 Minutes","blog/openclaw-telegram-setup",[1655,1656,1657,1658,1659,1660],"OpenClaw Telegram setup","connect OpenClaw to Telegram","OpenClaw Telegram guide","OpenClaw Telegram bot","OpenClaw Telegram not working","OpenClaw messaging channels","NvqUwglkjEPsoCAGNoGwH1FiBEvsi1nfM1q6Jx36Cvc",1778850199126]