ExcelMCP
The ExcelMCP server provides a live intelligence layer for AI agents to interact with Excel spreadsheets stored in OneDrive. It enables real‑time querying and analysis of data via the following capabilities:
Access a cached graph of the workspace including filenames, sheet names, column headers, relationships, and naming variants.
Rescan the OneDrive folder to update the structure index and embeddings when files or structures change.
Answer natural language questions by dynamically routing to relevant sheets, fetching live data, and returning results.
Filter specific sheets from OneDrive based on exact matches, substring containment, comparisons, date bounds, or null checks.
Perform grouped aggregations (sum, count, mean, min, max) on a single sheet with optional pre‑filtering and post‑aggregation filtering.
Aggregate data across multiple files for totals, sums, counts, or averages, accounting for naming variations.
Inspect a single file to retrieve its structural metadata (sheet names, column headers, approximate row counts).
Join two sheets live on key columns, either inferred from relationships or explicitly specified.
Calculate net values over transaction types across different components with specified signs.
Read the value of a specific cell by address or named range.
Perform semantic lookups to find a single cell value anywhere in the workspace using natural language queries or explicit key‑value pairs, returning the value with provenance and confidence.
Automatically configures the ExcelMCP server for use with Windsurf, enabling AI agents to query and analyze live Excel files stored in OneDrive through natural language and structured tools.
Automatically configures the ExcelMCP server for use with Hermes, enabling AI agents to query and analyze live Excel files stored in OneDrive through natural language and structured tools.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ExcelMCP What's the total profit on the Q2 P&L sheet?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ExcelMCP
A live Excel intelligence layer for AI agents. Point it at a OneDrive folder and your agent can ask questions about those spreadsheets in plain English, against the numbers that are in them right now.
The problem this solves
Most spreadsheet integrations work by copying your data somewhere else. They ingest the workbook, chunk it, embed the cell values, and store the whole thing in a vector database. From that moment on your agent is answering questions about a snapshot. Someone updates the inventory sheet at 9am and the agent is still quoting Tuesday's numbers.
ExcelMCP splits the problem in two.
Structure gets cached. Filenames, sheet names, column headers, where the header row starts, which columns hold dates, how sheets relate to each other — plus a small sample of distinct labels per low-cardinality column, which is what makes routing work across a hundred near-identical sheets. This changes rarely, it is cheap to store, and it is what the agent needs in order to know what to ask for. (The sampled labels are the one place structure touches values; the exact boundary is spelled out in What lands on disk.)
Data never gets cached. Every tool call that returns a number goes out to the Microsoft Graph API and pulls it live. There is no data cache to go stale, no sync job to fall behind, and no answer ever served from disk.
Every response carries a metadata.fetched_at timestamp and an is_cached: false flag so the model can see, in band, that it is looking at fresh data.
Related MCP server: Microsoft 365 MCP Server
How it works
A natural language question gets embedded, matched against the sheet descriptions by cosine similarity, then reranked by lexical overlap with column names and sampled values — which is what keeps routing meaningful when twenty workbooks share one schema. Those sheets, and only those, get fetched live. Filtering and aggregation then happen in pandas on the freshly fetched frame. Single-value questions skip the row pipeline entirely: lookup reads one key column and one row and returns the cell with its provenance.
Requirements
Python 3.10 or newer
A Microsoft 365 account with OneDrive
uv, or plain pip if you prefer
Install
From the repository root:
git clone https://github.com/Karunya-Muddana/ExcelMCP.git
cd ExcelMCP
uv sync # install dependencies
uv build # build the wheel
pip install dist/excelmcp-0.3.0-py3-none-any.whlOr install straight from source without building:
pip install .There is no compiler step and no native extension to build. Vector search runs on a NumPy cosine scan rather than hnswlib, specifically so that pip install works on a machine with no C++ toolchain.
Setup
Run the wizard once:
excelmcp-setupIt walks through four things:
Microsoft device-flow sign in. You get a code, you paste it into the browser, the token cache lands in
~/.excelmcp/token.jsonwith0600permissions.Which OneDrive folder to index, for example
/ERP.A scan of every
.xlsxin that folder to build the structure graph and the embeddings.Detection of the AI agents already installed on your machine, and a written config entry for the ones you pick.
Agents it can configure automatically
Agent | Config file |
Claude Code |
|
Claude Desktop |
|
Cursor |
|
Windsurf |
|
Gemini CLI |
|
Codex CLI |
|
VS Code (Copilot) | VS Code user |
Cline | extension |
Continue |
|
Goose |
|
Zed |
|
Hermes |
|
Existing config files are backed up before they are touched. If your agent is not on the list, the wizard prints the exact JSON or TOML block to paste in yourself.
Other wizard commands
excelmcp-setup list-agents # show what was detected
excelmcp-setup install --only cursor # register with one agent, skip the rescan
excelmcp-setup doctor # diagnose a broken install
excelmcp-setup uninstall # remove ExcelMCP from every agent config
excelmcp-setup --folder /ERP --yes # fully non-interactive
excelmcp-setup --dry-run # print the changes, write nothingTools exposed to the agent
Tool | Network | What it does |
| none | Full structure of the workspace: files, sheets, columns, table regions, relationships, naming variants, scan age. Instant. |
| none | Same, narrowed to one file, with approximate row counts as of the last scan. Instant. |
| heavy | Re-crawls OneDrive and rebuilds structure, sampled values, relationships, embeddings. |
| live | Natural language question, routed by vector similarity plus lexical rerank. |
| live | One call → one cell value with file/sheet/cell provenance and a confidence signal. |
| live | One addressed cell in one Graph request. |
| live | Fetch one sheet, return rows matching conditions. |
| live | Fetch one sheet, group and reduce it, with |
| live | Fetch matching sheets from every file, fold into a total. |
| live | Merge two sheets on key columns, suggested from known relationships. |
| live | Signed sum over transaction types — net stock in one call. |
The two structure tools are free and instant because they read the local graph. Everything marked live goes to the API on every single call.
Usage
Once the server is registered, you mostly just talk to your agent normally. Under the hood it makes calls like these.
Orient first. The agent should always do this before guessing at a column name, since no two companies name things the same way:
get_workspace_graph(folder_path="/ERP")Ask a question without knowing where the answer lives:
query("what are the top 10 products by sales value", folder_path="/ERP")Filter a known sheet:
filter_sheet(
file_name="Inventory.xlsx",
sheet="Stock",
conditions={"Status": "Low", "Quantity": "<50"},
folder_path="/ERP",
sort_by="Quantity",
limit=100,
)Supported condition operators, all ANDed together:
Form | Meaning |
| exact match — case- and whitespace-insensitive; pass |
| contains, literal substring, not a regex |
| greater than (also |
| date bound, ISO-8601, works on detected date columns |
| any of the listed values |
| inclusive range, numeric or date |
| combined bounds |
| null check — blanks and empty strings count as null |
A column name or operator that does not exist raises an error rather than quietly returning zero rows, which is the failure mode that makes an agent confidently report the wrong thing. When conditions legitimately match nothing, the response carries zero_match_diagnostics — what each condition matched on its own, plus up to twenty values actually present in the offending column — so a near-miss gets corrected instead of reported as "no data".
Ask for a single figure in one call:
lookup(query="contracted rate for Titanium Dioxide under the BESTEX contract",
folder_path="/Contracts")The answer comes back with provenance — file, sheet, cell address, the matched row — and a confidence field. Multiple matching rows return ambiguous with every row; sheets that disagree return conflict with every version and no value; a misspelled key returns fuzzy suggestions. The tool never returns a bare number.
Group and reduce inside one file:
aggregate(
file_name="Sales.xlsx",
sheet="Q1",
group_by="Region",
value_col="Revenue",
operation="sum",
folder_path="/ERP",
)Total the same sheet across every file in the workspace:
cross_file_aggregate(
sheet="Q1",
value_col="Revenue",
operation="sum",
folder_path="/ERP",
conditions={"Status": "Closed"},
)cross_file_aggregate returns a per-file breakdown alongside the total, plus skipped_files when a file could not be read and unmatched_files — with did_you_mean candidates — for every file that does not contain the exact sheet name. That way a partial total is visibly partial instead of silently wrong, including the case where the sheet is named Sales in some files and Sales 2024 in others. Check sheet_name_variants in get_workspace_graph before aggregating to see that fragmentation up front.
Agent playbook
Getting the server installed is the easy half. The agents/ folder covers the other half: how to prompt an agent that has these tools, how to wire it into each host, and what to automate once it works.
A drop-in system prompt for custom agents, subagents, | |
Copy-paste prompts sorted by job: orientation, straight answers, analysis, verification, reporting, data quality. Ends with a set of anti-prompts, the reasonable-looking phrasings that reliably produce wrong answers. | |
A first session that proves the chain works end to end, including how to verify for yourself that the data really is live. | |
What gets written to each of the twelve supported host configs, how to verify it, per-host quirks, and how to drive the server programmatically with no host at all. | |
Which tool to reach for, how semantic routing actually picks a sheet, what the condition syntax cannot express, and the data shapes that produce confident wrong answers. | |
Symptoms decoded, from PATH problems and 403s through to garbled column names and totals that come out double. | |
Four ready-to-schedule routines: daily inventory check, weekly sales digest, month-end reconciliation, data quality audit. Each with the prompt, the scheduling, and what tends to go wrong. |
Guardrails built into the server
The server ships a set of operating rules in its MCP instructions, which the host model reads before it makes its first call. They exist because these are the specific ways an LLM gets spreadsheet questions wrong:
Never assume a filename, sheet name, or column name. Discover it from the graph.
Never add up cross-file numbers mentally. Call
cross_file_aggregateand let the tool do it.Never reach for
openpyxl,pandas.read_excel, or the local filesystem. The files are not on this machine.Never sum a quantity column in transaction-style data raw — use
derivewith the transaction types spelled out.Date columns arrive as ISO-8601 strings, already converted from serials by the server. Never do serial arithmetic by hand.
For a single figure, call
lookupand cite the provenance it returns; surface itsambiguousandconflictoutcomes instead of picking a value.Check the
truncatedandtotal_matchedfields before claiming a result is complete.
Hosts that ignore server instructions, and custom agents you build yourself, need this stated in their own prompt. See agents/system-prompt.md.
Configuration
Variable | Default | Purpose |
| built in | Azure AD application client ID |
|
| Tenant. Use |
| unset | Folder to use when a tool call omits |
|
| Maximum simultaneous Microsoft Graph requests, across every code path. |
The built in client ID is a public client used for device-code flow. It carries no secret, it is visible in every auth request by design, and it is safe to have in this repository. Swap it for your own app registration if you want the consent screen to carry your organisation's name.
What lands on disk
~/.excelmcp/
token.json MSAL token cache. Auth material only, written 0600.
graph.json Structure graph: item IDs, sheet names, column headers,
used-range dimensions, date column types, per-sheet
table regions, inferred and formula-declared
relationships — and sampled values (see below).
vectors.npy Embedded sheet descriptions for semantic routing.
metadata.json Labels and lexical terms tying each embedding to a sheet.
relationships.yaml Optional, written by you: declared join relationships.The honest version of the no-cache claim, as of 0.3.0. No row of your
data, no cell grid, and no queryable value is stored on disk — every answer
is served from a live fetch, always. There is one deliberate exception:
graph.json stores sampled values, up to 50 distinct text labels per
low-cardinality column (client names, statuses, material names, units),
captured at scan time. They exist so that a hundred structurally identical
sheets are distinguishable when routing a question, so that lookup can find
which sheet contains "BESTEX" without downloading everything, and so that
relationships can be inferred from value overlap rather than assumed from
column names. They are routing evidence, not a data cache: nothing ever
answers a question from them, and a workspace scan refreshes them wholesale.
The graph also stores a per-sheet structure fingerprint (header columns and
used-range address) purely to detect drift, and — new in 0.3.0 — a region
map: the row spans of each table body on a sheet, derived from the ranges the
sheet's own SUM/COUNT/AVERAGE formulas refer to, plus the addresses any
cross-sheet formula reads. Those are row numbers and cell addresses, not
contents; no value is read to produce them. A region's label, where present,
is the second deliberate exception alongside sampled values: a few words read
from the section-banner cell immediately above a region ("NAPHTHALENE",
"OLEUM 65%"), kept so the model can name which table it means instead of
guessing from row numbers. It is structural metadata describing the sheet's
layout, not row data — the same distinction sampled values already draw. If
any of this is more than you want on disk, don't scan that folder; if you want
to verify the boundary, graph.json is small and readable, so go look.
On Windows, os.chmod only toggles the read-only bit, so the 0600 mode is a best effort there and the real protection is the default per-user ACL on %USERPROFILE%. On macOS and Linux the mode is applied to the temp file before any content is written to it, so the token never briefly exists as world readable.
Tests
# offline unit tests, no network and no credentials required
pytest tests/test_unit.py
# live integration tests against a workspace you have already scanned, opt in
EXCELMCP_TEST_FOLDER=/ERP pytest tests/test_live_integration.py -vThe integration suite skips itself when EXCELMCP_TEST_FOLDER is unset, so a plain pytest run stays offline.
Project layout
agents/ prompts, host guides, and schedulable routines
auth.py MSAL device flow, token cache, proactive refresh
graph_client.py Graph API wrapper, 429 backoff, shared concurrency gate
structure.py Structure discovery, value sampling, relationship inference
embeddings.py FastEmbed vectors, NumPy cosine search, lexical rerank
query_engine.py Conditions, live fetch, aggregation, joins, derive
lookup.py Single-cell lookup pipeline and get_cell
ranges.py A1-notation range arithmetic
main.py FastMCP tool definitions and server entry point
cli.py Setup wizard, agent detection, config writing
agents.py Per agent config formats and file locations
storage.py Atomic writes, stderr logging, config directory handlingContributing
Issues and pull requests are welcome. If you are adding support for another agent, agents.py is the only file you should need to touch: add an AgentSpec with the config path, the entry shape, and a detection hint.
License
MIT. See LICENSE.
Available Tools
11 toolsaggregateA
Fetches a sheet LIVE and runs a grouped aggregation. Operations: sum, count, mean, min, max. group_by is one column name or a list of them. conditions filters rows before aggregating (same grammar as filter_sheet, including the object form). having filters the AGGREGATED rows afterwards, e.g. having={"Revenue": ">1000"} keeps only groups whose aggregate exceeds 1000. SINGLE FILE ONLY. For totals across multiple files you MUST use cross_file_aggregate instead — never use this tool and then manually add results across files. Get column names from get_workspace_graph first. Returns rows plus a truncated flag. If conditions matched zero rows, zero_match_diagnostics shows what each condition matched alone and the values actually present — correct the condition and retry.
Inputs: sheet (required), group_by (required), file_name (required), operation (required), +4 more. Returns: object
cross_file_aggregateA
MANDATORY for any total spanning more than one file. Fetches relevant sheets from ALL files in PARALLEL, applies filter conditions, returns the aggregate total.
WHEN YOU MUST CALL THIS:
Any total, sum, count, or average across multiple files
Any cross-file comparison or consolidation
Verifying a total you calculated from individual files
NEVER calculate cross-file totals by:
Adding individual filter_sheet results in your head
Using Python to sum numbers from separate tool calls
Guessing based on partial data
Always call this AND show per-file breakdown so the user can verify both agree. If they differ, flag it.
ONLY files whose sheet is named EXACTLY sheet are
included in the total. Files without that exact sheet
are listed in unmatched_files, with their actual sheet
names and did_you_mean candidates — they are NEVER
silently included. If the response has a warning,
skipped_files, or unmatched_files, surface that to the
user: the total may be incomplete. Check
sheet_name_variants in get_workspace_graph first to see
naming fragmentation before aggregating.
Inputs: sheet (required), operation (required), value_col (required), conditions, +1 more. Returns: object
deriveA
Computes a NET value over transaction types in one call: sum of sign * groupwise_sum(quantity_col) across the given components. This is how a stock figure like receipts + purchases − consumption − returns becomes ONE call with the arithmetic done in pandas, instead of five filter_sheet calls added up in your head (which RULE 3 forbids).
components is a list of {"conditions": {...same grammar as filter_sheet...}, "sign": 1 or -1, "label": "receipts"} conditions (optional) pre-filters the sheet before any component applies. The response includes a per-component breakdown with rows_matched. A component that matched ZERO rows is flagged and warned about — check the spelling of the transaction type before trusting the net.
Inputs: sheet (required), group_by (required), file_name (required), components (required), +3 more. Returns: object
filter_sheetA
Fetches a specific sheet LIVE from OneDrive and returns rows matching the given conditions. Always live — no cache. Use when you already know which file and sheet to query. Get column names from get_workspace_graph first.
Condition formats (string form): Exact match: {"ColumnName": "value"} Contains: {"ColumnName": "~value"} (literal, not regex) Comparisons: {"ColumnName": ">100"} (also >=, <, <=) Date bounds: {"Batch Date": ">=2026-01-01"} (ISO-8601)
Condition formats (object form, combinable): IN list: {"Status": {"in": ["Closed", "Shipped"]}} Range: {"Qty": {"between": [10, 500]}} Date range: {"Batch Date": {">=": "2026-01-01", "<": "2026-04-01"}} Null check: {"Notes": {"is_null": false}} Contains: {"Name": {"contains": "oxide"}}
Multiple conditions are ANDed together; multiple operators inside one object are ANDed too. An unknown column name or operator is an error, not an empty result.
MATCHING IS NORMALISED, NOT STRICT: exact string matches ignore case and surrounding whitespace ("closed" matches "Closed "), because Excel cells carry stray whitespace constantly. Pass exact_case=true for byte-for-byte matching. Contains (~) is case-insensitive. If zero rows match, the response includes zero_match_diagnostics showing what each condition matched on its own and the values actually present in the column — use it to correct a near-miss and retry instead of concluding the data does not exist. At most 1000 rows are returned; check the truncated and total_matched fields in the response.
Inputs: sheet (required), file_name (required), conditions (required), limit, +3 more. Returns: object
get_cellA
Reads EXACTLY ONE cell, LIVE, by address. One Graph request, tiny payload, no ambiguity. Use when the location is already known — follow-up questions, scheduled routines, anything where lookup or filter_sheet already established the address earlier. address is A1 notation ("B7") or the name of a workbook-scoped named range that resolves to one cell. Serial dates arrive converted to ISO-8601; check resolved_type. A multi-cell address is an error — use filter_sheet for ranges.
Inputs: sheet (required), address (required), file_name (required), folder_path. Returns: object
get_workspace_graphA
Returns the cached file structure — all filenames, sheet
names, column headers, and cross-sheet relationships
(inferred at scan time from matching column names plus
overlapping sampled values, merged with any the user
declared in ~/.excelmcp/relationships.yaml; each carries
a confidence score and its evidence).
INSTANT — makes no API call. Reads from local graph.json.
ALWAYS call this first at session start to orient yourself.
Shows you exactly which files exist, what sheets they have,
and what columns are in each sheet. The structure varies
for every company — never assume, always discover.
Also returns sheet_name_variants: groups of sheet names
that differ only in case or whitespace across files —
check it before any cross-file operation, because those
match by exact sheet name.
Each sheet carries a regions list: the table bodies found
in it, derived from the sheet's own SUM/COUNT formulas, in
absolute sheet rows. A sheet with more than one region holds
several separate tables (also listed in multi_region_sheets),
so a plain aggregate over it adds up blocks that were never
meant to be summed — read its unclaimed_rows and check which
region you mean before totalling anything.
layout_confidence is "unconfirmed" wherever the region map
came from formulas alone and nothing has verified it.
Use this before any filter_sheet call when unsure which
file or column to query.
Inputs: folder_path. Returns: object
inspect_fileA
Returns structural metadata for one specific file — sheet names, column headers, and each sheet's approx_row_count AS OF THE LAST SCAN (this tool makes no API call, so the count is not live; treat it as an order-of-magnitude hint, not a current figure). INSTANT — reads from cached graph.json. Use before filter_sheet when you need to confirm the exact column names available in a specific file.
Inputs: file_name (required), folder_path. Returns: object
join_sheetsA
Joins two sheets LIVE on key columns and returns the merged rows, with filter_sheet's truncation contract (total_matched, truncated, limit). Omit left_on/right_on to let the server pick keys from the workspace's known relationships — it uses a declared or high-confidence inferred relationship and REFUSES with the candidate list when confidence is low, rather than guessing. The keys actually used and their source are in data.keys. Key matching is normalised (case, whitespace, 45 vs 45.0); null keys never join. join_type: inner, left, right, outer. Colliding column names get _left/_right suffixes. Use this instead of stitching filter_sheet results together yourself.
Inputs: left_file (required), left_sheet (required), right_file (required), right_sheet (required), +5 more. Returns: object
lookupA
ONE-CALL semantic lookup: finds a single cell value anywhere in the workspace and returns it WITH PROVENANCE (file, sheet, cell address, the matched row) and a confidence signal. Reads only the key column and the matched row — never whole sheets.
Two ways to call it:
Natural language: lookup(query="contracted rate for Titanium Dioxide under the BESTEX contract"). The server resolves the key value against values sampled at scan time and picks the return column lexically. Works best when the query contains a literal value that appears in the data (a client, a material).
Explicit: lookup(key_column="Material", key_value= "Titanium Dioxide", return_column="Contracted Rate"). Use this when the query form reports it could not parse, or for values too rare to be sampled. scope={"file": ..., "sheet": ...} narrows the search.
READ confidence BEFORE using the value: "high" — single row matched; corroborating sheets (if any) agree. provenance.corroborated_by lists them. "ambiguous" — the key matched SEVERAL ROWS. value is null; every row is in alternatives. Never pick one silently. "conflict" — several sheets DISAGREE. value is null; every version is in alternatives. Surface the conflict to the user. found=false — key not found; suggestions holds fuzzy near-misses (retry with exact spelling), or ambiguity explains why routing failed. NEVER present a value from this tool without citing provenance.file, provenance.sheet and provenance.cell.
Inputs: query, scope, key_value, key_column, +2 more. Returns: object
queryA
Natural language question with automatic RAG routing. Embeds your question, retrieves candidate sheets by vector similarity, reranks them by lexical overlap with column names and sampled values, fetches the winners LIVE from OneDrive, and returns results. Use for exploratory questions when you do not know which specific file or sheet contains the answer. n_results controls how many sheets are fetched (default 5); min_score drops weak matches. CHECK data.routing: when routing_ambiguous is true the top candidates scored within a tie margin and the choice between them is effectively arbitrary — confirm with inspect_file or ask the user instead of trusting one. Including a distinctive literal value in the question (a client name, a material) strongly improves routing. Response metadata.fetched_at confirms this is live data. For known file/sheet combinations use filter_sheet instead.
Inputs: question (required), min_score, n_results, folder_path. Returns: object
scan_workspaceA
Rescans the OneDrive folder and rebuilds the structure index and embeddings. SLOW — makes many API calls. ONLY call when: new .xlsx files have been added to OneDrive, or existing sheet names or column headers have changed. DO NOT call this at session start. DO NOT call this before every query. The workspace is already indexed from setup. Use get_workspace_graph for instant structure access.
Inputs: folder_path. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
Each tool targets a distinct operation: structure discovery, metadata inspection, rescanning, natural-language query, filtered row fetch, grouped aggregation, cross-file totals, joins, signed net calculations, single-cell address reads, and semantic cell lookup. The descriptions include explicit guidance on when to use each tool and warn against alternatives (e.g., aggregate vs. cross_file_aggregate). There is no meaningful overlap or ambiguity between tool purposes.
All tool names follow a consistent verb_noun pattern in snake_case: get_workspace_graph, inspect_file, scan_workspace, filter_sheet, join_sheets, get_cell, etc. Short verb-only names like query, aggregate, derive, and lookup are also consistent in style and fit the pattern of using a single verb when the object is implied. No camelCase or mixing of conventions.
With 11 tools, the server is well-scoped for an Excel workspace analysis tool. Each tool serves a clear and necessary purpose, covering discovery, querying, aggregation, joining, and cell-level access. The count is comfortably within the 3-15 range and does not feel bloated or sparse.
The tool surface covers the full read/analysis lifecycle: workspace structure discovery (get_workspace_graph, inspect_file, scan_workspace), flexible data retrieval (query, filter_sheet, get_cell, lookup), grouped aggregation (aggregate), multi-file totals (cross_file_aggregate), complex net computations (derive), and joins (join_sheets). There are no obvious missing operations for the apparent purpose of reading and analyzing Excel data.
Related MCP Connectors
Official Microsoft MCP Server to query Microsoft Entra data using natural language
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Teable is an AI spreadsheet for business that combines a familiar spreadsheet interface with a structured database. Its remote MCP server lets AI agents inspect project and table structure, read and update records, and access the Teable API through OAuth with existing project permissions. Website: [teable.ai](https://teable.ai)
Remote streamable-HTTP MCP server running on a single Cloudflare Worker. Your assistant gets live Airbnb, Amazon, Booking.com, Google Flights, Maps and Reddit data, social search on X, Instagram and TikTok, the Meta Ad Library, and image/video generation without any keys. Connect your own accounts to let it send WhatsApp or Telegram messages, work an IMAP inbox, manage Meta Ads campaigns and publish to X and LinkedIn. OAuth 2.1 with PKCE; stored credentials are AES-256-GCM encrypted.
Related MCP Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol server that enables AI assistants to read from and write to Microsoft Excel files, supporting formats like xlsx, xlsm, xltx, and xltm.61,051MIT
- AlicenseBqualityAmaintenanceA Model Context Protocol server that enables interaction with Microsoft 365 services (Excel, Calendar, Mail, OneDrive, Teams, etc.) through the Graph API, allowing AI assistants to manage Microsoft 365 resources via natural language.20391,108 npm1,159MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI agents to create, read, and modify Excel workbooks without requiring Microsoft Excel installation.MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables AI agents to freely operate Excel spreadsheets, providing tools for workbook creation, cell manipulation, formatting, formula handling, and data export.11ISC