# 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.

Source: https://elaichi.ai/connectors/devto/

## Facts

| | |
| --- | --- |
| Application | Dev.to |
| Category | Marketing Automation |
| AI tools | 7 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Dev.to is connected

- 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

## Connect Dev.to in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Dev.to.
2. Optionally set Share with, then press Connect.
3. Paste a Dev.to API key. One person generates a token in Dev.to and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Dev.to tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Dev.to MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Dev.to MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

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.
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.

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

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Dev.to tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Dev.to through Elaichi

### Turn a release note into a Dev.to draft

Developer Relations. 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.

### See what is published and what is waiting

Marketing. 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.

### Fix a typo without opening the editor

Content. 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.

### Check which launch posts are already live

Product. 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.

### Draft a tutorial straight from a Cursor session

Engineering. 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.

### Summarize the last month of Dev.to posts

Community. 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.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one Dev.to connection?

Yes. One person connects Dev.to in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so every article created or updated in Dev.to is logged against the person who asked for it.

### 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.

## All 7 Dev.to tools

Every tool below is callable through https://api.elaichi.ai/mcp once Dev.to is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Dev.to me** (List). Get the Dev.to profile of the user who owns the API key (id, username, name, summary, location, website).
- **List all Dev.to articles** (List). List all of the user's own Dev.to articles, drafts and published, newest drafts first.
- **Get single Dev.to article by ID** (Get). Get a single published Dev.to article by its numeric id. Drafts are not returned here; find them with articles list or draft-articles list.
- **Create a Dev.to article** (Create). Create a Dev.to article from Markdown. Wrap fields under `article`. Set `published: false` to save a draft or `true` to publish immediately. Up to 4 tags.
- **Update a Dev.to article by ID** (Update). Update one of the user's Dev.to articles by id. Wrap fields under `article`. Set `published: true` to publish a draft, or `false` to move a published article back to draft.
- **List all Dev.to published articles** (List). List the user's published Dev.to articles, newest first.
- **List all Dev.to draft articles** (List). List the user's unpublished (draft) Dev.to articles.
