# How to connect DEV Community to OpenClaw (paste one key, 28 tools) > Connect DEV Community to OpenClaw with ClawLink: paste your DEV Community key once and 28 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/devto The usual route to DEV Community 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 DEV Community setup: install one ClawHub skill, connect DEV Community in the browser, and OpenClaw can call real DEV Community 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 DEV Community. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect DEV Community** — 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 devto # connect DEV Community (browser OAuth) npx -y @useclawlink/cli actions devto # list available actions npx -y @useclawlink/cli run devto --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 DEV Community in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your DEV Community API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from DEV Community, 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 DEV Community is connected in the dashboard, that agent calls the same 28 DEV Community 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). ## DEV Community MCP for OpenClaw Looking for a DEV Community MCP server for OpenClaw? ClawLink connects DEV Community to OpenClaw and exposes 28 DEV Community 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 DEV Community integration](https://claw-link.dev/hermes/devto) works the same way. ## What the OpenClaw DEV Community integration can do 28 DEV Community tools are ready for OpenClaw once the account is connected. ### All 28 DEV Community tools for OpenClaw | Tool | What it does | |---|---| | **Get article** `devto_get_article` | Returns a single published article by its ID, including full body content | | **Get article by path** `devto_get_article_by_path` | Returns a single published article by username and slug path | | **Get comment** `devto_get_comment` | Returns a single comment and its descendants (replies) by comment ID | | **Get current user** `devto_get_current_user` | Get the currently authenticated user's profile information | | **Get listing** `devto_get_listing` | Returns a single classified listing by its ID | | **Get organization** `devto_get_organization` | Returns a single organization by its username | | **Get profile image** `devto_get_profile_image` | Returns the profile image URL for a user or organization by username | | **Get user** `devto_get_user` | Get a single user by their ID or username | | **List articles** `devto_list_articles` | Returns a list of published articles, optionally filtered by tags, username, state, or top | | **List comments** `devto_list_comments` | List comments for a specified article or podcast episode on DEV Community | | **List followed tags** `devto_list_followed_tags` | Returns a list of tags followed by the authenticated user | | **List followers** `devto_list_followers` | Retrieve a list of users who follow the authenticated user | | **List latest articles** `devto_list_latest_articles` | Retrieve a list of published articles sorted by descending publish date | | **List listings** `devto_list_listings` | Returns a list of classified listings for jobs, mentors, products, etc | | **List listings by category** `devto_list_listings_by_category` | Returns a list of classified listings filtered by category | | **List organization articles** `devto_list_organization_articles` | List articles published by a specific organization on DEV.to | | **List organization users** `devto_list_organization_users` | List users belonging to a specified organization on DEV.to | | **List podcast episodes** `devto_list_podcast_episodes` | Retrieve a list of podcast episodes from DEV.to | | **List reading list** `devto_list_reading_list` | Returns the articles in the authenticated user's reading list | | **List tags** `devto_list_tags` | Returns a list of tags with their names, background colors, and text colors | | **List user all articles** `devto_list_user_all_articles` | List all articles (both published and unpublished) for the authenticated user | | **List user articles** `devto_list_user_articles` | List published articles for the authenticated user | | **List user published articles** `devto_list_user_published_articles` | Returns a list of the authenticated user's published articles only | | **List user unpublished articles** `devto_list_user_unpublished_articles` | Returns a list of the authenticated user's unpublished (draft) articles | | **List videos** `devto_list_videos` | Retrieve a list of articles that contain videos | | **Create article** `devto_create_article` | Create a new article on DEV Community | | **Update article** `devto_update_article` | Update an existing article on DEV Community | | **Update listing** `devto_update_listing` | Updates an existing classified listing on DEV Community | ## Example prompts **Get Article** > Pull the relevant data from DEV Community, summarize it in plain English, and point out anything that needs attention. **Get Article By Path** > Pull the relevant data from DEV Community, summarize it in plain English, and point out anything that needs attention. **Get Comment** > Pull the relevant data from DEV Community, summarize it in plain English, and point out anything that needs attention. **Get Current User** > Pull the relevant data from DEV Community, 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 DEV Community working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the DEV Community API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected DEV Community 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 DEV Community. | 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 DEV Community actions to the runtime in a format your agent can reliably use. | 28 tools for DEV Community are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes DEV Community 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 DEV Community in the browser, and the 28 tools above work from chat. There is no SDK and no config file, and the DEV Community 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 DEV Community skill but can't call the tools The ClawHub skill teaches OpenClaw about DEV Community, but the calls run through the ClawLink plugin and your connected account. Make sure DEV Community 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 DEV Community 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 DEV Community tools DEV Community 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 DEV Community 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. ### DEV Community 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 DEV Community has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw DEV Community integration? Yes. ClawLink is the fastest way to connect OpenClaw to DEV Community: link your DEV Community account once in the browser and OpenClaw can call the DEV Community API through 28 ready-made tools — no custom code or token handling. ### How do I add DEV Community to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink DEV Community skill from ClawHub, then you click Connect in the dashboard to authorize DEV Community. OpenClaw calls the tools from the next message — no config files, and the DEV Community key you paste is stored server-side instead of in your environment. ### How long does it take to connect DEV Community to OpenClaw? About two minutes. Sign in, click Connect next to DEV Community in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring DEV Community 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 DEV Community working from chat. ### OpenClaw installed the DEV Community skill but can't call the tools The ClawHub skill teaches OpenClaw about DEV Community, but the calls run through the ClawLink plugin and your connected account. Make sure DEV Community 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 - [GitHub tools](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [Connect PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [Connect SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.