Can I reference a database by name instead of its id?

Yes. notion_read_database accepts either the database id or its name, so you can just say "read my Content Calendar database" and the AI will resolve it.

Does this need a Notion API key?

No. LMCP reads the cached Notion data locally on your Mac through the native integration — there are no API keys to configure and nothing is sent to an external server.

Are the database properties typed correctly?

Yes. Rows are mapped through the database schema, so select fields, dates, checkboxes, people and relations come through as real typed values rather than raw text.

Read a Notion Database with AI on Mac

The notion_read_database tool lets your AI assistant read the rows of a Notion database straight from your Mac, with every property mapped through its schema. Pass the database id or its name, and the AI gets back the records as structured data it can reason over. You type something like: "Read my Content Calendar database in Notion and tell me which posts are still in Draft status." The AI pulls the cached rows, reads the Status, Date and Author properties, and answers in plain language — no copy-paste, no jumping into the Notion UI.

Because the schema is applied, select fields, dates, checkboxes, relations and people come through as real typed values instead of raw blobs, so the AI can filter, sort and summarize accurately.

Which AI agents work?

LMCP exposes 150+ tools to any MCP-capable assistant:

Desktop clients — Claude Desktop, Cursor, VS Code (GitHub Copilot), Windsurf and Zed auto-configure through a local stdio connection. Nothing to wire up by hand.
Web AIs — Claude.ai, ChatGPT, Grok and Perplexity connect through the LMCP Cloud Relay connector, which bridges the web assistant to the server running on your Mac.

The same notion_read_database tool is available everywhere once LMCP is installed.

Automation

Reading a database is the starting point of richer workflows. The AI can chain it with other LMCP tools:

Read a tasks database, then create Reminders or Calendar events from rows due this week.
Pull a CRM database and draft follow-up emails in Mail for each contact in the pipeline.
Read a project tracker and post a status update to Slack or Teams.
Export filtered rows into an Excel or PowerPoint file for a weekly report.

You describe the outcome once; the AI orchestrates the steps.

Context

The AI is working with your real Notion data on your real Mac — not a sandbox or a stale paste. It sees your actual databases, your current rows, your property names. That means answers reflect what is true right now, and the assistant can reference specific records by name when it replies.

Productivity

Manually scanning a Notion database — opening it, applying filters, reading down a column, tallying values — eats minutes every time. With notion_read_database, a question like "how many deals are over $10k and unassigned?" is answered in seconds. Stand-up prep, status rollups, and "what's overdue?" checks that used to need a manual pass through the board become a single sentence to your AI. Over a week of repeated lookups, that adds up to real hours back.

Privacy & GDPR

Everything runs locally on your Mac. LMCP reads the cached Notion data on your machine and hands it to your AI client — no copy of your database is uploaded to or stored on any LMCP server. There are no API keys to hand over and no third-party cloud in the loop. This is privacy by architecture, not by policy. Learn more about being GDPR-compliant by architecture.

Ready to give your AI access to your Notion databases? Download LMCP — it's free and native to macOS.