Grape

cool.grapePublished by grape.coolOfficial publisherv1.0.0Updated Oct 26, 2026

Read and write the notes and folders of your Grape account, the AI note-taking app.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote MCP endpoint for Grape, the AI note-taking app, letting an assistant read and write the notes and folders in your Grape account.

What you can do
  • Read notes and folders in a connected Grape account
  • Create and edit notes, and organize them into folders
  • Work with the account's note structure through the Grape MCP endpoint
When to use it
Useful when you keep notes in Grape and want an assistant to look things up, draft or update notes, and keep folders organized without switching apps.
Requirements
A Grape account and OAuth authorization to the remote endpoint at mcp.grape.cool; no local package, environment variables or headers are declared.
Before you install
The server can write to your notes and folders, so changes may alter or reorganize existing content. Access is granted through OAuth to your Grape account, so review the permissions you approve.

Installation

In SourceWeft

  1. Open Grape in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/cool.grape%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "grape": {
      "type": "http",
      "url": "https://mcp.grape.cool/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 17, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.