Dev.to MCP connector
The Dev.to connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent read, draft, and update Dev.to articles as the person who signed in, with every action recorded in an audit log.
- Connects with an API key
- Free 14-day trial
- No credit card
List my Dev.to drafts that have not been published yet
Working in Dev.to with Elaichi
-
List all Dev.to me
-
List all Dev.to articles
-
Get single Dev.to article by ID
How to connect Dev.to to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Dev.to MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Dev.to MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Dev.to MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Dev.to MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Dev.to MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Dev.to to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Dev.to through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Dev.to is logged.
-
Developer Relations
Turn a release note into a Dev.to draft
Paste the release note into the chat and ask for a Dev.to article. The draft lands in your Dev.to account, unpublished, ready for a read-through before it goes live.
-
Marketing
See what is published and what is waiting
Ask for the list of published Dev.to articles and the list of drafts side by side. You get a clear picture of what is out and what is still sitting in the queue.
-
Content
Fix a typo without opening the editor
Ask the agent to update a specific Dev.to article with the corrected sentence. The change goes in under your name, and the audit log records exactly what was edited.
-
Product
Check which launch posts are already live
Before a launch call, ask which Dev.to articles about the feature are published and which are still drafts. No tab switching, no scrolling through the dashboard.
-
Engineering
Draft a tutorial straight from a Cursor session
After working through a setup in Cursor, ask it to write the steps up as a Dev.to draft. The tutorial is saved to your Dev.to account for review before anyone sees it.
-
Community
Summarize the last month of Dev.to posts
Ask for a roundup of the articles your account published in the last thirty days, with titles, tags, and publish dates. Paste the summary into your community newsletter.
Try asking
- “List my Dev.to drafts that have not been published yet”
- “Draft a Dev.to article announcing the new webhooks feature”
- “Update the onboarding tutorial article with the new install command”
What connecting Dev.to gets you
6 screens from Elaichi, each doing one job for your Dev.to account.
Ask Elaichi to work across your apps.
List my Dev.to drafts that have not been published yet
Draft a Dev.to article announcing the new webhooks feature
Update the onboarding tutorial article with the new install command
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about your Dev.to articles in plain words.
Get answers from live Dev.to drafts and published posts, no dashboard required.
Copy the endpoint
AI apps
One endpoint brings Dev.to to every client.
Claude, ChatGPT and Cursor connect over OAuth, no SDK and no shared API key.
Tool catalog
7 Dev.to tools, ready without writing code.
List, read, create and update articles, drafts and published posts straight away.
Toolboxes
Every team gets its own Dev.to toolbox.
Scope what Developer Relations, Marketing and Content can reach in Dev.to.
Shared connections
Teammates publish through Dev.to without the key.
One person connects, shares with teams, and nobody else ever sees the API key.
Audit log
Every Dev.to edit answers who did what.
When, who, what happened, type and resource, in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Dev.to digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch articles
Dev.to
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Dev.to
Queued
Workflows
A schedule drafts your Dev.to digest itself.
Articles are fetched, grouped, drafted, approved by a person, then posted back to Dev.to.
Dev.to health
Refreshed 4 minutes ago · every 15 minutes · from the articles collection
Articles
1,284 ↓ 12%
Drafts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Articles created
Last 14 days
By team
Share of activity
DevRel 34%
Marketing 27%
Content 21%
Product Launches 18%
Collections and dashboards
Dev.to health, computed without asking a model.
Four metrics, 14 days of articles created, and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Dev.to
All three can connect Dev.to to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Dev.to tools | Allow or restrict single Dev.to tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Dev.to call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Dev.to tools for your AI agents
7 tools are ready to call through Elaichi's MCP endpoint the moment you connect Dev.to, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Dev.to to Claude?
In Elaichi, choose Dev.to and paste the API key from your Dev.to settings page, which is the whole sign-in step. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and your Dev.to articles are available in the chat.
Does Dev.to work with ChatGPT and Cursor as well as Claude?
Yes. Dev.to is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is pasted into Claude, ChatGPT, Cursor, Microsoft Copilot, or any other MCP client. The Elaichi Agent uses the same connection with nothing extra to set up.
What can an AI agent actually do with my Dev.to data?
It can list your Dev.to articles, show which are published and which are still drafts, open a single article to read it, write a new draft, and update an article you already have. In practice that means asking for a roundup of recent posts, asking for a draft from a release note, or asking for a correction to a live article. Short, concrete asks work better than long sentences.
Does connecting Dev.to give the AI everything in my account?
A Dev.to API key belongs to one account, so the agent only sees the articles and drafts that account can see, and only acts as that person. Elaichi can narrow that further with restrictions on individual actions, but it can never widen access beyond what the person already has in Dev.to.
Can I stop an agent from deleting or changing things in Dev.to?
This Dev.to connector has no way to delete an article at all, so deletion is not a risk. Creating and updating Dev.to articles can each be restricted separately, on a role or on one person, so a team can read and summarize without being able to write. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a Dev.to connection when someone leaves?
Offboarding a person in Elaichi ends their access to Dev.to at once, across Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client. A shared Dev.to connection keeps working for everyone else on the team. If you want the connection gone entirely, disconnecting Dev.to once in Elaichi removes it from every client.
Does the Dev.to MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Dev.to is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Dev.to?
Yes. Both let Claude, ChatGPT or Cursor use Dev.to. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Dev.to call.
How is Elaichi different from Composio for Dev.to?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Dev.to: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Dev.to in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot