Planner & To Do

Læs siden på dansk The Planner & To Do connector gives your AI read-only access to Microsoft Planner and Microsoft To Do. Your AI can read the Planner plans the connected user is a member of, with their buckets and tasks, find the user’s own tasks across plans, and read and search the user’s To Do lists. You connect with your Microsoft work account, and your AI never sees the access itself.

• Price: 149 DKK/month excl. VAT (€19/month if you have chosen the EU · EUR market in the portal). No lock-in, cancel at any time. The price covers 1 user and 1 agreement (one connected Microsoft user). Each extra user and each extra agreement costs 74.50 DKK/month excl. VAT (€9.50). Also included in the Consile Studio membership and the free edition. See Pricing.
• Users: whoever buys Planner & To Do automatically gets the included access. If more colleagues need the connector in their AI, an administrator gives them access under Team in the portal (choose All tools next to Planner & To Do on the person’s page). An extra user is billed pro rata from the day access is given. A colleague without access can still see the tools in their AI, but every lookup is refused with a message to ask an administrator for access. If you have the Consile Studio membership, an administrator instead gives one membership licence per person, and it also covers Planner & To Do. See Team.
• Multiple Microsoft users: the portal calls each connection to the system an agreement. One agreement is one connected Microsoft user, because Planner memberships and To Do lists belong to the individual user. If your AI should also read a colleague’s plans and To Do lists, or you have several Microsoft organizations, an administrator adds another agreement with Add agreement on the Connections card on the connector’s page in the portal. Each agreement gets its own address, for example https://mcp.consile.ai/planner-2/mcp, which you add as a separate connector in your AI. Under the Consile Studio membership and in the free edition, other rules apply to adding an agreement. See Connect Planner & To Do.
• Endpoint: https://mcp.consile.ai/planner/mcp (your own named connector in your AI).

​

What does it require?

• A Microsoft work or school account. You log in with an account in your organization at Microsoft. A personal Microsoft account cannot be used.
• Planner and To Do in the user’s Microsoft 365. The user who connects must have a Microsoft 365 licence that includes Planner and To Do. Your AI only sees the plans and lists that this user can see.
• Possibly an administrator’s approval. In many organizations, Microsoft requires an administrator to approve Consile before a regular user can connect. See Connect Planner & To Do.

​

Prerequisites

​

Read-only

When you connect, you approve three permissions at Microsoft:

• Tasks.Read: read the user’s Planner tasks and To Do lists.
• User.Read: read the connected user’s own profile, so the portal can show who the agreement is connected with.
• offline_access: keeps the connection alive.

Both Microsoft permissions are pure read permissions. Consile therefore cannot create, change, move or complete tasks, not even outside the tools. In addition:

• The connector has no write tools. All ten tools can only read.
• Consile only sends read requests to Microsoft.
• If one of the permissions is missing from Microsoft’s approval, the connection is refused.

​

The agreement follows the connected user

Planner and To Do are personal. An agreement always reads as the Microsoft user who connected it:

• Your AI sees the Planner plans the connected user is a member of, and that user’s To Do lists.
• list_my_tasks shows the tasks assigned to the connected user. This applies no matter which colleague in Consile is asking.
• All colleagues with access to the connector in Consile read through the same connected user.

If every employee should have their own tasks in their AI, each one needs their own agreement, connected with their own Microsoft account.

​

Assignees are shown as ids, not names

Planner stores who a task is assigned to as Microsoft user ids (long ids such as <user id>), not as names. The connector does not ask for access to your user directory, so your AI cannot look up the names and must not guess them. This means:

• Ask for “my tasks” rather than a specific colleague’s name. Then your AI uses list_my_tasks.
• If you want to see a colleague’s tasks in a plan, your AI can filter on the colleague’s user id. A Microsoft administrator can find the id (Object ID) on the user in the Microsoft Entra admin center.

​

What can it do? (tools)

You do not need to know the tool names. You ask in natural language, and your AI picks the right one itself. The connector has ten read-only tools: six for Planner and four for To Do. When your AI calls them, they are called planner__<tool> (for example planner__list_my_tasks).

​

Try asking

​

Limitations

• Read-only: the connector cannot create, change, move or complete tasks in Planner or To Do. See Read-only.
• Work accounts only: personal Microsoft accounts are not supported.
• Only the connected user’s tasks: your AI only sees the plans and lists the connected user has access to. See The agreement follows the connected user.
• No names for assignees: assignees, creators and whoever completed a task are shown as user ids. See Assignees are shown as ids, not names.
• Large plans: a list of Planner tasks returns at most 500 tasks. If there are more, the answer is marked as cut off. Narrow it down by bucket, status or assigned user.
• To Do in pages: To Do tasks and lists are fetched in pages of 50 rows by default and at most 500. A list’s rows show at most the first 2,000 characters of a description. get_todo_task shows up to 20,000 characters.
• Searching To Do: search_todo_tasks returns at most 200 hits and goes through every list, so it can take a little while when there are many lists. Completed tasks are left out unless you ask for them.
• No files: get_task shows links and attached files with their address, but the connector does not fetch the files themselves.
• The user’s permissions apply: if the connected user lacks access, or your administrator has not approved the permission the tool needs, Microsoft answers with an error (403), and your AI is told about it. Reconnecting does not help. Instead, ask a Microsoft 365 administrator for access.
• Microsoft’s call limit: Microsoft limits how many calls can be made in a short time. If a lookup hits the limit, your AI is told to wait a little and ask for fewer rows.
• Explanatory errors, but not always: for the common errors, the connector gives your AI an explanation: an access that must be connected again, missing permissions, an id that does not exist, and a request that Microsoft refuses. Other errors, for example a timeout or an error at Microsoft, only give the general error “Tool invocation failed.”
• The access is renewed automatically, but can stop: if the renewal fails, or Consile is removed in your Microsoft organization, your AI is told that the connection must be set up again from the Consile portal. The portal can still show Connected, because the stored access is still there. Only an administrator can reconnect: if the agreement says Access revoked, click Reconnect. Otherwise the administrator chooses Disconnect in the menu next to the agreement and then clicks Connect. You can also ask your AI for a new connection link in the connector that belongs to the agreement (for example planner-2). See Connect Planner & To Do.

Is something not working as expected? See Troubleshooting.