Cursor
Add Keep to your MCP configuration, then follow the authentication prompt.
{
"mcpServers": {
"keep": {
"url": "https://mcp.hykeep.app/mcp"
}
}
}Keep, where you already work
Connect once, approve access, and bring your Keep workspace into the conversation. Ask for the plan. Pick up the work. Save what comes out of it.
The Keep MCP connector gives your agent access to the records you’re allowed to use. Sign in and approve the connection when prompted.
Make sure you have a Keep workspace.
Add Keep in your agent client using the endpoint shown here.
Complete sign-in and consent, then ask your agent to list your projects.
claude mcp add --transport http --scope user keep https://mcp.hykeep.app/mcphttps://mcp.hykeep.app/mcpUse a remote HTTP MCP connection. Keep uses OAuth; you don’t paste a workspace API key.
Add Keep to your MCP configuration, then follow the authentication prompt.
{
"mcpServers": {
"keep": {
"url": "https://mcp.hykeep.app/mcp"
}
}
}Add this to your workspace’s .vscode/mcp.json and approve the connection.
{
"servers": {
"keep": {
"type": "http",
"url": "https://mcp.hykeep.app/mcp"
}
}
}Add the remote server, then authenticate to your Keep workspace.
codex mcp add keep --url https://mcp.hykeep.app/mcp
codex mcp login keepBring Gemini into the same project through its remote MCP connection.
gemini mcp add --transport http keep https://mcp.hykeep.app/mcpIn Gemini CLI, use /mcp auth keep to complete sign-in.
This setup is for Gemini CLI. Gemini CLI connection guide
Beyond coding
Use a custom remote connector to bring Keep into everyday conversations. Ask for the project plan, capture a meeting outcome, or save the document you just drafted.
Add https://mcp.hykeep.app/mcp as a custom connector, then sign in to Keep.
Use Keep as a custom MCP app where your ChatGPT plan and workspace settings support it. Add the same Keep endpoint and authorize your workspace.
Availability and administrator approval depend on your ChatGPT workspace. The official guide covers the current setup.
ChatGPT’s custom app guideKeep connects through remote HTTP MCP with OAuth. These clients document that connection pattern. Availability can depend on your client version and your team’s settings.
Add Keep in your MCP configuration with a serverUrl, then use the client’s authentication action to sign in.
{
"mcpServers": {
"keep": {
"serverUrl": "https://mcp.hykeep.app/mcp"
}
}
}For Cascade, add a remote server in MCP settings using serverUrl, then complete OAuth. The Devin Local agent uses its own configuration.
{
"mcpServers": {
"keep": {
"serverUrl": "https://mcp.hykeep.app/mcp"
}
}
}In Settings → AI → MCP Servers, add a remote server with Keep’s URL. Zed prompts you to authenticate.
{
"context_servers": {
"keep": {
"url": "https://mcp.hykeep.app/mcp"
}
}
}Using another client? Look for remote HTTP MCP and OAuth support, then add https://mcp.hykeep.app/mcp. A client that only runs local MCP servers needs a compatible bridge. These examples follow vendor documentation; individual Keep sign-in flows have not all been tested end to end.
A connected agent can read the requirement, work on its task, and leave a summary and the next step in Keep.
ONB-189OpenAdd the per-person cost to the export
ONB-189In progressWorking on ONB-189
a41c9e2 illustrativeFree trial · 14 days
Bring your team and your AI agents into one shared workspace. Sign in to your workspace or start a free trial.