← All updates

New feature

Asire MCP server: let your AI assistant work with your tasks

Your tasks already live in Asire. Now the AI assistants you use can work with them directly. The Asire backend ships with a built-in MCP server, so an assistant can look up what's on your plate, add a task, or check off a subtask without you copying anything back and forth.

What is MCP?

The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to other apps through a defined set of tools. Instead of pasting text into a chat, the assistant calls a tool, such as "list the tasks in this project", and gets structured data back. Asire now offers that connection at /mcp on the API.

What an assistant can do

The first release includes ten tools, grouped by what they do:

  • Look around: list_workspaces, list_projects, list_tasks, and get_task walk from your workspaces down to individual tasks.
  • Search: search_workspace runs a full-text search across a workspace.
  • Create and update tasks: create_task adds a task with a title, description, priority, and due date. update_task_status moves it between To Do, In Progress, In Review, and Completed.
  • Work with subtasks: list_subtasks shows a task's checklist, add_subtask adds an item, and update_subtask edits one or ticks it off.

That covers requests like "What's still open in the website project?", "Create a high-priority task to renew the SSL certificate, due Friday", or "Break that task into three subtasks and mark the first one done."

Your permissions still apply

Every tool runs as you. The MCP server does not have a back door: each call goes through the same code the Asire app uses, so workspace membership and your project's Who can update tasks setting are enforced on the server. An assistant can only see projects you can see, and it can only change tasks you are allowed to change.

Deliberately left out for now: deleting anything, workspace administration, moderation, and the Secret Vault. Vault contents are zero-knowledge and stay readable only in your own browser.

A few details we got right

  • Safe subtask edits: updating a subtask changes only the fields you pass. Ticking one off won't wipe its title or note.
  • Clear tool descriptions: each tool explains its inputs, including the exact status and priority values, so assistants pick the right one the first time.
  • Read-only tools are marked as such, so MCP clients can allow them without asking each time.
  • Stateless by design, so the server scales across instances the same way the rest of the API does.

Connecting an assistant

You connect with a normal sign-in. There is no token to copy and paste. In your assistant's connector settings, add a custom connector (or custom MCP server) and enter Asire's MCP address, which is your Asire API address followed by /mcp. Then:

  • The assistant opens an Asire page in your browser.
  • Sign in to your Asire account if you aren't already.
  • Review the request. The page names the assistant, shows where you'll be sent back to, and lists what it can and can't do.
  • Choose Allow. You're returned to the assistant, which is now connected.

In Claude Code, the same thing is one command, claude mcp add --transport http asire https://<your-asire-api>/mcp, followed by /mcp to sign in.

Asire uses the standard sign-in method for MCP (OAuth 2.1 with PKCE and dynamic client registration), so any assistant that supports remote MCP servers with sign-in can connect. We've built it to the open specification rather than for one product. Support for adding custom connectors varies by assistant and plan, so check your assistant's documentation for where it lives.

How your account stays protected

  • You approve every connection. Nothing connects until you click Allow on an Asire page you signed in to.
  • Access is limited to MCP. The token an assistant receives works only with the MCP server. It cannot call the rest of the Asire API.
  • Short-lived and renewable. Access tokens expire after an hour and refresh in the background. If a refresh token is ever reused, Asire revokes that whole connection.
  • Nothing sensitive is stored in the clear. Asire keeps only hashed copies of the codes and tokens it issues.
  • Suspended or deleted accounts lose access immediately, the same as in the app.

See and disconnect your assistants

Open Settings and choose Assistants to see every assistant connected to your account and when you connected it. Choose Disconnect next to any of them and it loses access within about a minute. You can connect it again whenever you like.

What's next

Next we'll look at comments, editing task details, and more tools for chat and meetings.