# Send Email From Devin

Devin CLI and Devin Local, the agent in Devin Desktop, read MCP servers from the same config files. Add Inboxjot once from the terminal, sign in, and Devin can send email, read delivery status and draft campaigns.

## Add the Server

Run this in your terminal:

```bash Terminal
devin mcp add -s user inboxjot --url https://mcp.inboxjot.com
```

`-s user` writes the server to `~/.config/devin/mcp_config.json`, so it works in every project. Without `-s`, Devin saves it to `.devin/mcp_config.local.json` in the current project, which git ignores. Use `-s project` to write it to `.devin/mcp_config.json` and share it with your team.

## Sign In

```bash Terminal
devin mcp login inboxjot
```

Devin opens Inboxjot in the browser and refreshes the sign-in on its own after that. In Devin Desktop, the server shows Needs auth in the MCP list until you sign in. Choose Authenticate there to sign in from the app.

Inboxjot then asks you to pick a workspace and the access the tool gets. See [Access](https://inboxjot.com/docs/mcp.md#access).

## Check the Connection

```bash Terminal
devin mcp list
```

`devin mcp get inboxjot` shows the details of the server.

Devin asks you to approve each MCP tool call by default. To approve the read tools for good, add them to `permissions.allow` in your Devin config, for example `mcp__inboxjot__list_emails`. Keep `send_email` on ask, because it sends real email.

## Try It

- “Send a test email from <hello@yourdomain.com> to me with the subject Hello.”
- “Which emails bounced in the last 24 hours, and why?”
- “Add a trial ending email to this app and send me one with Inboxjot.”
- “Check that my sending domain passes SPF, DKIM and DMARC.”

## Remove the Server

```bash Terminal
devin mcp remove inboxjot
devin mcp logout inboxjot
```

`logout` deletes the stored sign-in. To cut access from the Inboxjot side, revoke the tool on the MCP page of the dashboard.