
Connect Prowlo to Zed
Zed supports remote MCP servers with the standard OAuth flow. Point it at the hosted Prowlo URL, sign in through your browser, and Zed's agent can search your Dataset and pull live Reddit context — the session is stored in your system keychain, so you sign in once.
Leave the headers empty
Zed triggers its OAuth flow when a remote server has no configured Authorization header. Add the URL on its own and Zed opens your browser to sign in — no API key to copy or rotate.
Prerequisites
- •Active Prowlo account with organization access
- •A recent Zed build — remote MCP OAuth support is required, so update Zed if the sign-in prompt never appears
Setup Guide
Add a remote server
Open Settings → AI → MCP Servers, click Add Server, and choose Add Remote Server.
Paste the Prowlo URL
Name the server prowlo and give it this URL. Leave the headers field empty:
https://api.prowlo.com/mcpSign in with OAuth
Zed sees the 401, runs OAuth discovery, and opens your browser. Sign in to Prowlo and approve the connection. Zed persists the session in your system keychain, so restarts do not send you through the flow again.
Verify the connection
Settings → AI → MCP Servers should show prowlo as running. Open the agent panel and ask:
Search my Prowlo dataset for posts about pricingEditing settings.json directly
Zed stores MCP servers under context_servers in settings.json. Open it with zed: open settings from the command palette and add:
{
"context_servers": {
"prowlo": {
"url": "https://api.prowlo.com/mcp"
}
}
}Not `mcpServers`
Configs copied from Claude Desktop or Cursor use a top-level mcpServers key. Zed will ignore it — the key here is context_servers.
Connecting with an API key instead
If you would rather not use OAuth — or you are on a machine with no browser — add an Authorization header. Generate a key at API Access — it is shown once.
{
"context_servers": {
"prowlo": {
"url": "https://api.prowlo.com/mcp",
"headers": { "Authorization": "Bearer prowlo_your_key_here" }
}
}
}Adding the header suppresses the OAuth prompt — Zed only offers sign-in when no Authorization header is configured.
Troubleshooting
The sign-in prompt never appears
- • Remove any
headersblock — anAuthorizationheader tells Zed to skip OAuth - • Update Zed; remote-MCP OAuth is a relatively recent addition and older builds time out silently instead
- • Fall back to the API-key config above if your build predates it
The server connects but the agent doesn't see the tools
- • Check the tool list in the agent panel and make sure Prowlo's tools are enabled for the current profile
- • Restart the server from
Settings → AI → MCP Servers
Authentication failed
- • Restart the server to re-run the OAuth flow and replace a stale keychain entry
- • On the API-key path, verify the key hasn't been revoked and starts with
prowlo_ - • Check that your trial or subscription is still active on Billing, or see the troubleshooting guide