home / mcp / reflect mcp connector server
Provides an stdio-based MCP server exposing Reflect tools for graphs, books, links, and notes.
Configuration
View docs{
"mcpServers": {
"akshayrawat-reflect-mcp-connector": {
"command": "npx",
"args": [
"-y",
"reflect-mcp-connector@latest"
],
"env": {
"REFLECT_CLIENT_ID": "<client-id>",
"REFLECT_ACCESS_TOKEN": "REDACTED",
"REFLECT_API_BASE_URL": "https://reflect.app/api",
"REFLECT_CLIENT_SECRET": "<client-secret>",
"REFLECT_DEFAULT_GRAPH_ID": "<optional>",
"REFLECT_OAUTH_REDIRECT_URI": "http://127.0.0.1:8787/callback"
}
}
}
}You can connect Reflect to any MCP-compatible client using an MCP server that runs over stdio, exposing practical Reflect tools for graphs, books, links, and notes. This guide shows you how to configure and use the Reflect MCP Connector with your MCP clients so you can access Reflect data and actions directly from your workflow.
You will connect your Reflect account to an MCP client by providing an access token and configuring the MCP server as a local stdio service. The server runs commands locally via your MCP client and exposes a focused set of Reflect tools for working with graphs, books, links, and notes.
Prerequisites: ensure you have Node.js version 20 or newer installed on your machine.
Install or use the MCP Connector through your MCP client as shown in the configuration examples. The server runs via a stdio command, typically using npx to fetch the latest package.
# If you prefer using npx to run the latest connector
npx -y reflect-mcp-connector@latestConfigure your MCP client with the Reflect access token and optional defaults. You can provide a default graph to avoid passing graph identifiers on every call.
OAuth helper (optional) lets you obtain an access token via a browser flow. It prints an access token you can paste into your MCP client configuration.
REFLECT_CLIENT_ID="..." REFLECT_CLIENT_SECRET="..." npx -y reflect-mcp-connector@latest auth loginServer configuration (required): set your Reflect access token and optional defaults.
OAuth helper configuration (optional): provide client id/secret and redirect URI if you plan to use the interactive login flow.
Never commit tokens or OAuth secrets. Prefer setting credentials in your MCP client configuration rather than relying on local files or working directories.
Tools exposed by the Reflect MCP Connector include the following endpoints for retrieving and creating Reflect content.
If you encounter connectivity issues, verify that you provided REFLECT_ACCESS_TOKEN correctly in your MCP client configuration and that the token has the necessary scopes. Use the helper commands to verify connectivity and retrieve your graph list.
Fetches information about the currently authenticated Reflect user and account.
Lists all graphs available in your Reflect account.
Lists books stored in Reflect associated with your graphs.
Lists links connected to your graphs or notes in Reflect.
Creates a new link within a Reflect graph.
Appends a daily note to the selected Reflect graph or workspace.
Creates a new note in Reflect within a specified graph.