Remove one-click deploy buttons, Deployment section, and render.yaml
Non-technical users are covered by the AI agent setup prompt. Technical users can follow Setup or Docker sections directly.
This commit is contained in:
@@ -2,9 +2,6 @@
|
|||||||
|
|
||||||
An MCP server that bridges IMAP/SMTP email accounts to [Poke](https://poke.com). Provides AI agents with tools to search, read, send, and manage emails, and automatically forwards new incoming emails to the Poke inbound endpoint.
|
An MCP server that bridges IMAP/SMTP email accounts to [Poke](https://poke.com). Provides AI agents with tools to search, read, send, and manage emails, and automatically forwards new incoming emails to the Poke inbound endpoint.
|
||||||
|
|
||||||
[](https://render.com/deploy?repo=https://github.com/kacperkwapisz/poke-mail)
|
|
||||||
[](https://railway.com/new/github?repo=https://github.com/kacperkwapisz/poke-mail)
|
|
||||||
|
|
||||||
## Features
|
## Features
|
||||||
|
|
||||||
- **12 MCP tools**: search, read, send, draft, archive, move, mark, list/create/rename/delete folders, server info
|
- **12 MCP tools**: search, read, send, draft, archive, move, mark, list/create/rename/delete folders, server info
|
||||||
@@ -155,30 +152,6 @@ The server is mostly idle (IMAP IDLE + lightweight HTTP). Recommended limits for
|
|||||||
| `POKE_API_KEY` | from config | Overrides Poke API key in config |
|
| `POKE_API_KEY` | from config | Overrides Poke API key in config |
|
||||||
| `PORT` | `3000` | HTTP server port |
|
| `PORT` | `3000` | HTTP server port |
|
||||||
|
|
||||||
## Deployment
|
|
||||||
|
|
||||||
### Docker (recommended)
|
|
||||||
|
|
||||||
The GitHub Actions workflow automatically builds and pushes to `ghcr.io` on every push to `main` and on tags.
|
|
||||||
|
|
||||||
1. Set repository secrets: none needed (uses `GITHUB_TOKEN` for GHCR)
|
|
||||||
2. Push to `main` or tag `v*` to trigger a build
|
|
||||||
3. Pull and run the image with your `config.yml` and `MCP_API_KEY`
|
|
||||||
|
|
||||||
### Render
|
|
||||||
|
|
||||||
Click the **Deploy to Render** button above, or manually:
|
|
||||||
|
|
||||||
1. Create a Web Service on Render connected to your repo
|
|
||||||
2. Fill in `IMAP_HOST`, `IMAP_USERNAME`, `IMAP_PASSWORD`, `POKE_WEBHOOK_URL`, and `POKE_API_KEY`
|
|
||||||
3. `MCP_API_KEY` is auto-generated — copy it for your Poke connection settings
|
|
||||||
|
|
||||||
For multi-account setups, mount a `config.yml` as a secret file instead of using env vars.
|
|
||||||
|
|
||||||
### Railway
|
|
||||||
|
|
||||||
Click the **Deploy on Railway** button above, then set the same environment variables as Render.
|
|
||||||
|
|
||||||
## Poke Setup
|
## Poke Setup
|
||||||
|
|
||||||
Connect your MCP server to Poke at [poke.com/settings/connections](https://poke.com/settings/connections). Add the bearer token (`MCP_API_KEY`) in the connection auth settings.
|
Connect your MCP server to Poke at [poke.com/settings/connections](https://poke.com/settings/connections). Add the bearer token (`MCP_API_KEY`) in the connection auth settings.
|
||||||
|
|||||||
-19
@@ -1,19 +0,0 @@
|
|||||||
services:
|
|
||||||
- type: web
|
|
||||||
name: poke-mail
|
|
||||||
runtime: docker
|
|
||||||
plan: free
|
|
||||||
autoDeploy: false
|
|
||||||
envVars:
|
|
||||||
- key: MCP_API_KEY
|
|
||||||
generateValue: true
|
|
||||||
- key: POKE_WEBHOOK_URL
|
|
||||||
sync: false
|
|
||||||
- key: POKE_API_KEY
|
|
||||||
sync: false
|
|
||||||
- key: IMAP_HOST
|
|
||||||
sync: false
|
|
||||||
- key: IMAP_USERNAME
|
|
||||||
sync: false
|
|
||||||
- key: IMAP_PASSWORD
|
|
||||||
sync: false
|
|
||||||
Reference in New Issue
Block a user