Quotewise Quote MCP

Pencarian kutipan semantik - 600 ribu kutipan dengan transparansi sumber

Lihat di quotewise.ioCoba MCP iniDisponsori

Dokumentasi

MCP Setup

Give your AI assistant access to 623K quotes with source transparency.

What you'll be able to do:

  • Search quotes by meaning, not just keywords
  • See sources for every quote via QuoteSightings
  • Works with Claude Code, Claude Desktop, ChatGPT, Codex CLI, Gemini CLI, and any MCP client

Most clients: one command. Claude Desktop config file: 2 minutes.

[!success] Success No signup needed to start. Anonymous access: 20 requests/day. For higher limits, create an API key or authenticate via OAuth device flow (prompted on first use).

Quick Setup (Any Client)

npx @quotewise/mcp setup

Interactive helper that generates config for your client. Or choose your client below.

Claude Code Setup

Run this command in your terminal:

claude mcp add --transport http quotewise https://mcp.quotewise.io/

Verify with claude mcp list or /mcp inside a session.

[!info] Info This adds Quotewise to your project-level .mcp.json. Use --scope user for global config.

Claude Desktop Setup

Method 1: Connectors UI (Recommended)

  1. Open Claude Desktop
  2. Go to Settings > Connectors
  3. Add the MCP server URL:

Method 2: Config File

Add to your config file using the mcp-remote bridge:

{
  "mcpServers": {
    "quotewise": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.quotewise.io/"]
    }
  }
}

Requires Node.js 18+. Auth via OAuth device flow on first connection.

[!info] Info Claude Desktop does not support remote HTTP servers directly in the config file. The mcp-remote bridge runs a local stdio process that proxies to the remote server.

Where is the config file?

macOS:

~/Library/Application Support/Claude/claude_desktop_config.json

Windows:

%APPDATA%\Claude\claude_desktop_config.json

Linux:

~/.config/Claude/claude_desktop_config.json

[!warning] Warning Note: After editing the config file, restart Claude Desktop for changes to take effect.

Learn more: Connect to Remote MCP Servers (official docs)

ChatGPT Setup

Available to Pro, Plus, Business, Enterprise, and Education accounts.

Connectors (Recommended)

  1. Open ChatGPT Desktop > Settings > Connectors
  2. Click Advanced, enable Developer Mode
  3. Click Create and enter the MCP server URL:
  4. In each new chat: click + > More > Developer Mode to activate Alternative: Custom GPT Actions (for building custom GPTs)

Add semantic quote search with source transparency to any custom GPT. Your GPT will find quotes by meaning and show sources for every result.

Step 1: Create Your GPT

  1. Go to ChatGPT > Explore GPTs > Create
  2. Click the Configure tab
  3. Under Actions, click Create new action

Step 2: Choose Authentication

[!warning] Warning Choose the right auth: Public GPT? Use OAuth. Private GPT (just you)? Use API Key.

Each user authenticates with their own Quotewise account.

Client ID

(Register at /register)
Or use Dynamic Client Registration

Client Secret

Leave empty (public client)

Authorization URL

https://quotewise.io/oauth/authorize

Token URL

https://quotewise.io/oauth/token

Scope

quotes:read

Token Exchange Method

Default (POST request)

API Key (Private GPTs only)

Only use for private GPTs where you control access.

Auth Type

API Key

API Key

Your Quotewise API key

Auth Header

Authorization

Custom Header Name

Bearer

Step 3: Import OpenAPI Schema

Click Import from URL and enter:

Step 4: Privacy Policy

Enter our privacy policy URL:

Step 5: GPT Instructions

Copy these instructions into your GPT's system prompt to prevent hallucination and ensure source transparency:

You help users find quotes from 500K+ quotes with source transparency via Quotewise.

## CRITICAL RULE
NEVER invent quotes. ALWAYS use Quotewise API. If search returns no results, say "I couldn't find a quote matching that." Don't fabricate or guess.

## Semantic Search (Primary Tool)
Use \`quotes_list\` with \`q\` parameter. This searches by MEANING, not keywords.

User describes what they want → you search that description → semantic vectors find conceptual matches.

Examples:
- "courage during uncertainty" finds Mandela, Roosevelt, etc.
- "persistence pays off" finds Edison, Jordan, etc.
- "question authority" finds Thoreau, Douglass, etc.

## Finding Specific Authors
1. \`originator_search\` → find author by name
2. \`originator_quotes\` → get their quotes

## Random Discovery
\`quote_random\` when users want inspiration without a specific topic.

## Similar Quotes
\`quote_similar\` (by quote ID) or \`quote_similar_by_text\` when users want more like a quote they like.

## Presenting Results
- ALWAYS show author name
- ALWAYS mention source/work if available (QuoteSightings provides this)
- Offer to find similar quotes or more from same author

## Why This Matters
People search quotes for different reasons—presentations, inspiration, research, personal use. Quotewise provides source transparency via QuoteSightings. Show users the evidence so they can decide for themselves.

See OpenAI's authentication docs for more details on OAuth setup.

Codex CLI Setup

Run this command in your terminal:

codex mcp add quotewise --url https://mcp.quotewise.io/

Verify with codex mcp list.

Gemini CLI Setup

Method 1: Command Line (Recommended)

Run this command in your terminal:

gemini mcp add --transport http quotewise https://mcp.quotewise.io/

Method 2: Manual Configuration

Edit the settings.json file directly:

{
  "mcpServers": {
    "quotewise": {
      "httpUrl": "https://mcp.quotewise.io/"
    }
  }
}

Auth via OAuth device flow on first connection.

Where is the config file?

macOS / Linux:

~/.gemini/settings.json

Windows:

%HOMEPATH%\.gemini\settings.json

Verify the Connection

  1. Restart the Gemini CLI if already running
  2. Enter chat mode by typing gemini
  3. Type /mcp to see connected servers
  4. You should see quotewise listed with status Connected

Try asking: "Get a quote regarding persistence"

Cursor IDE and Grok Bot

Same public MCP URL. Auth differs by host.

Cursor IDE / Claude

Headerless OAuth works. Add the public URL; the host opens a browser to Quotewise login.

https://mcp.quotewise.io/mcp

Grok Bot custom MCP

Headerless OAuth does not complete today. After Dynamic Client Registration succeeds, Authorize spins and never opens https://quotewise.io/oauth/authorize. That is a Grok Bot host limitation, not a missing Quotewise allow-list entry (grokbot://mcp/oauth/callback is already accepted).

Working customization: public URL, plus an optional qw_ Bearer header for a signed-in session.

{
  "url": "https://mcp.quotewise.io/mcp",
  "headers": {
    "Authorization": "Bearer qw_YOUR_TOKEN"
  }
}

Create a qw_ token on the developer dashboard. Omit the header for anonymous access (20 requests/day). Device-code OAuth is only started by clients that choose that grant; Grok Bot does not.

Other MCP Clients

Any MCP client that supports remote HTTP servers can connect using this configuration:

{
  "mcpServers": {
    "quotewise": {
      "url": "https://mcp.quotewise.io/"
    }
  }
}

Exact config format varies by client. The URL is always https://mcp.quotewise.io/.

Cursor IDE and Claude complete headerless OAuth in a local browser. Grok Bot custom MCP does not; use the public URL plus an optional qw_ Bearer header. Some CLI clients start OAuth device flow on first use.

Troubleshooting

Connection refused or timeout

  • Verify you can reach https://mcp.quotewise.io/ from your network
  • Corporate firewalls may block the connection
  • For the Claude Desktop config file method, ensure Node.js 18+ is installed (required by mcp-remote)

Invalid authentication token

  • API tokens use the qw_ prefix. Regenerate your key at the developer dashboard
  • Cursor IDE and Claude open a browser for headerless OAuth. Grok Bot custom MCP does not; pass Authorization: Bearer qw_… instead
  • Some CLI clients start OAuth device flow. If prompted, open the URL and enter the displayed code
  • Anonymous access (20 requests/day) works without any authentication

Rate limit exceeded

Tools not appearing

  • After adding the server config, restart your MCP client
  • Use the ping tool to verify connectivity
  • See the MCP Tools Reference for the full list of available tools