Senpilot (Preview)

Ask regulatory questions and work with dataset extractions from Senpilot.

This connector is available in the following products and regions:

Pilot

Pilot connects Microsoft 365 Copilot and Copilot Studio agents to Senpilot's regulatory intelligence for energy and utility teams. Ask Pilot a regulatory question and get a sourced answer drawn from regulator filings, decisions, and consultations. List the completed dataset extractions your Senpilot account can access, read their extracted rows, and edit individual rows in datasets you own.

Publisher: Senpilot Website: https://senpilot.com Support: hello@senpilot.com Privacy policy: https://senpilot.com/privacy Terms of use: https://senpilot.com/terms

Prerequisites

You will need the following to proceed:

• A Senpilot account. Pilot only exposes data the signed-in user can already see in the Senpilot app.
• A Copilot Studio environment with generative orchestration enabled on the agent.

Getting started

1. Add the Pilot tool to your agent from the tool catalog.
2. Select Create new connection. A Senpilot sign-in window opens.
3. Sign in with your Senpilot credentials and approve the requested access.
4. Select the new connection for the tool and add it to your agent.

Pilot uses OAuth 2.0. Each user connects with their own Senpilot account, and access tokens are refreshed automatically.

Supported operations

The MCP server exposes the following tools:

ask_pilot_reg

Ask Senpilot's Pilot a regulatory question. Returns a thread id plus either the completed, sourced answer or in_progress while Pilot continues working. A full answer usually takes 60 to 120 seconds, so the first response is normally in_progress. The agent then polls get_pilot_reg_results with the thread id every 5 to 10 seconds until the status is completed or failed, or 3 minutes have elapsed. Pass the same thread id to continue an existing conversation.

get_pilot_reg_results

Poll for the result of a previously started ask_pilot_reg call. Returns in_progress while Pilot is still working, the completed answer with its sources, or failed with a message if the run ended without an answer.

list_completed_dataset_extractions

List the completed dataset extractions the signed-in user can access, including datasets shared by teammates. Supports cursor-based paging.

get_dataset_extraction_rows

Read a page of extracted rows from a completed dataset extraction. Works for datasets the user created and datasets shared with them.

edit_dataset_extraction_rows

Add, update, soft-delete, or restore a single row in a completed dataset the user owns. Every change is recorded in the dataset's edit history. The tool requires explicit user confirmation before it makes a change, and the agent asks the user to confirm before calling it.

Known issues and limitations

• Very long regulatory answers may need a follow-up prompt. The agent polls get_pilot_reg_results for up to 3 minutes. If Pilot is still working after that, the agent says so and offers to check again. Ask it to check the result and it resumes with the same thread id.
• Reconnect after connector changes. If the tool page reports that the connection is no longer valid after the connector definition changes, remove the tool from the agent and add it again with a new connection. Refreshing the tool list alone does not recover.
• Use a standard agent. The Copilot for Microsoft 365 agent type does not invoke MCP tools from its test pane. Test with a standard Copilot Studio agent.
• Edits are limited to datasets you own. edit_dataset_extraction_rows rejects datasets shared with you by a teammate. Reads work on both.
• One row per edit call. Bulk edits are not supported; the agent makes one call per row.
• Data access follows your Senpilot permissions. Pilot never returns data the signed-in user cannot see in the Senpilot app.

Actions

Senpilot