Microsoft Excel 365
Connect AI agents and workflows to Excel 365: tables, rows, ranges, worksheets, charts and named items in workbooks on OneDrive and SharePoint.
Book a demoMicrosoft Excel 365 for AI agents and workflows.
engini lets your AI agents and workflows work in Excel 365 workbooks on OneDrive and SharePoint: read and update ranges, add and delete table rows and columns, create tables and worksheets, filter and sort, add and update charts and read them as images, and work with named items. Finance still runs on spreadsheets; engini connects them to the systems of record behind them. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.
Cursor, your code
audit log
in engini
What your agent can do in Microsoft Excel 365. Every tool is one you allow or leave out.
The Microsoft Excel 365 tools in engini, grouped by what they change. Read tools are safe to hand out widely. Write and delete tools go only to the agents that need them.
Read
Read the data.
Find workbooks and sheets.
Read charts, as data or as an image.
Find the drive that holds a workbook.
Write
Write data.
Build structure.
Sort and filter.
Chart the data.
Group many changes in one session.
Delete
Remove rows, columns or sheets.
Any endpoint
Call the Microsoft Graph Excel API, with the sign-in added for you.
Triggers
There are no Excel triggers. Start the workflow on a schedule, or when a file changes in OneDrive.
Connect your AI agent to Microsoft Excel 365. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your Microsoft Excel 365 connection and only the tools you choose. Add its address to your client and sign in through engini. There is no key to copy.
MCP client setup →Python and TypeScript
Hand your agent a toolset of Microsoft Excel 365 tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.
SDK guide →For coding agents
The engini CLI connects Microsoft Excel 365 and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.
CLI guide →Any language
Every Microsoft Excel 365 tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.
API reference →.cursor/mcp.json. Claude Code: claude mcp add.// .cursor/mcp.json: Cursor, connected to Microsoft Excel 365 through engini
{
"mcpServers": {
"engini-microsoft-excel-365": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your Microsoft Excel 365 connection and the tools this agent may use, then paste its address. The client signs in through engini on first use. Claude, VS Code and other clients take the same address: see the MCP client setup guide.
Each request runs through the Microsoft Excel 365 tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on Microsoft Excel 365. Agents and workflows, across systems.
Trackers that fill themselves
Every morning, add yesterday's invoices and payments from the ERP to the team's Excel tracker.
Actuals into the model
Actuals from SAP or Dynamics 365 update the forecast workbook, and the chart goes to Teams.
A workbook as the input
Rows added to a shared workbook become records in the ERP, and the row gets the record number.
Questions about a workbook
An agent in Claude reads a workbook and answers questions. Its toolset holds read tools only.
Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between Microsoft Excel 365 and another system engini connects is available.
You decide what each agent may do in Microsoft Excel 365. engini enforces it on every call.
Only the tools you allow
A toolset lists the Microsoft Excel 365 tools an agent may call and the connection each one uses. Give one agent read tools only and another the write it needs. engini refuses any call outside the toolset.
Scoped when you set them up
An MCP server exposes only the connections and tools chosen when it is created, and engini shows who uses each server.
Whose permissions apply
Connect a person's own Microsoft Excel 365 account and engini acts as that person, with their Microsoft Excel 365 permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.
Kept out of prompts
Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.
Every call on record
Every call lands in History and the audit log, which you can export or stream to your SIEM.
Test before production
Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.
Connect Microsoft Excel 365 in three steps. Then decide what each agent may do.
Sign in to Microsoft Excel 365
Add an Excel 365 connection and sign in with your Microsoft account, then point the tools at a workbook in OneDrive or SharePoint.
Choose the tools
Add the connection to an MCP server or a toolset with only the tools each agent needs.
Build or ask
Use the connection as a step in a workflow, or ask your agent to work in Microsoft Excel 365 from Claude, ChatGPT, Cursor or your own code.
Microsoft Excel 365 and engini. Straight answers.
Can an AI agent write to Microsoft Excel 365, or only read?
Both. engini has tools to update ranges, add and delete rows and columns, create tables and worksheets, sort, filter and chart. Whether a given agent may use them is up to you: give it a toolset or an MCP server with read tools only, and it cannot call the rest.
Does the agent act as me in Microsoft Excel 365?
It acts as the Microsoft account behind the connection, with that account's access to workbooks. Every run is recorded under the person who started it.
What if the tool I need is not listed?
Use Send API Request to call any Microsoft Excel 365 API endpoint through the same connection, and give it only to the agents that need it.