Blog
The MCP1 blog
Launches, guides to rolling out MCP across a company, and how we build MCP1 at Appwrite.
Announcement7 min read
Introducing MCP1: the gateway we built for ourselves
MCP1 started as an internal tool at Appwrite: one URL that connects every Appwriter’s agent to the systems we run on. Today we’re opening it to every team.
Eldad FuxFounder and CEO, AppwriteGuide4 min read
How to connect MCP servers to Grok Bot
Stop adding MCP servers to Grok Bot one at a time. Connect them all at once and use the same set across your coding agents.
Atharva DeosthaleDeveloper AdvocateGroups
- EngineeringFull
- SuccessRead-only
- DevRelRead-only
Rules
*__delete_*Admins only*__send_*Ask first
Guide6 min read
10 steps for rolling out MCP across your company
What we’d do again after rolling out MCP1 across Appwrite: a group for each team, read-only tokens first, rules that ask a human, and an audit log to tune by.
Eldad FuxFounder and CEO, AppwriteEngineering6 min read
How we built MCP1 on Appwrite
MCP1 runs on a single Appwrite project, with its OAuth2 server for every MCP client, Teams for workspaces and one function that decides every call.
Eldad FuxFounder and CEO, Appwrite