Fruitask MCP Integration
Connect Fruitask to AI assistants like Codex, Claude Desktop, Claude Code, Cursor, and VS Code Copilot using the open Model Context Protocol (MCP). Let your AI read and act on your workspaces, tables, notes, folders, calendars, Boards, and Automations — securely, with your own API key.
What is MCP?
The Model Context Protocol is an open standard that lets AI applications connect to external tools and data sources. The Fruitask MCP server exposes your account's data as a set of tools the AI can call — so you can ask things like “summarize my open tasks”, “add a note for tomorrow's standup”, or “create a calendar event next Monday”, and the assistant executes them through Fruitask.
Server endpoint
Use the Fruitask Streamable HTTP endpoint for Codex and modern MCP clients:
https://backend.fruitask.com/api/mcpLegacy SSE: https://backend.fruitask.com/api/mcp/sse. Existing SSE connections remain supported.
Discovery (server info + tool list): https://backend.fruitask.com/api/mcp/info
Authentication
Every request is authenticated with a Fruitask API key sent as a Bearer token. Create one in Account → API & Integrations. Each key has scoped permissions (read / write / delete) and an optional expiry — the MCP tools you can call are gated by your key's scopes.
Quick setup
Codex
Add this to your Codex config.toml, then restart the MCP connection:
[mcp_servers.fruitask]
url = "https://backend.fruitask.com/api/mcp"
[mcp_servers.fruitask.http_headers]
Authorization = "Bearer fk_YOUR_API_KEY_HERE"
Claude Desktop
Add this to your claude_desktop_config.json:
{
"mcpServers": {
"fruitask": {
"url": "https://backend.fruitask.com/api/mcp",
"headers": {
"Authorization": "Bearer fk_YOUR_API_KEY_HERE"
}
}
}
}
Generic MCP client (Streamable HTTP)
Any MCP-compatible client (Cursor, VS Code, custom agents) can connect with:
Endpoint (Streamable HTTP): https://backend.fruitask.com/api/mcp
Header: Authorization: Bearer fk_YOUR_API_KEY_HEREReplace fk_YOUR_API_KEY_HERE with a key from your account. Restart the client after adding the server.
Available tools
33 toolslist_files | Search and page through files owned by your account. |
get_file | Get an account file and its public or fresh private download link. |
list_workspaces | List accessible workspaces, including folder sharing. |
get_workspace | Read a workspace and its accessible tables. |
query_table | Search, sort and page visible native table rows. |
get_row | Read a visible row with column names. |
list_notes | List accessible notes, including folder sharing. |
get_note | Read a note and its content blocks. |
search | Search accessible workspace names, note titles and rows. |
list_folders | List owned and explicitly shared folders. |
list_calendars | List owned and shared calendars. |
get_calendar_events | Read event and recurring-series definitions. |
list_boards | List Boards in an accessible workspace. |
get_board | Read a Board and a page of its canvas objects. |
list_automations | List workspace Automations without credentials. |
get_automation | Read an Automation with stored credential fields omitted. |
get_automation_capabilities | Discover supported trigger and action types. |
create_row | Create a native table row with column defaults. |
update_cell | Update a permitted editable cell. |
upload_file | Upload a file to your account storage and return its public or private URL. |
create_note | Create a note with content and checklist blocks. |
add_block | Insert a content or checklist block. |
create_calendar_event | Create a single calendar event. |
update_calendar_event | Update a single unmanaged calendar event. |
create_board | Create a private Board with canvas objects. |
update_board | Update a Board using its latest updatedAt version. |
create_automation | Create a paused Automation draft. |
update_automation | Save an Automation as a paused draft. |
set_automation_enabled | Explicitly enable or pause an Automation. |
delete_row | Soft-delete a permitted native table row. |
delete_calendar_event | Delete a single unmanaged calendar event. |
delete_board | Move a Board to trash. |
delete_automation | Permanently delete an Automation and its execution logs. |
Permissions & scopes
Tools are grouped by the permission they require. Your API key's scopes decide which tools the assistant can use:
- read list and fetch workspaces, tables, rows, notes, folders, calendars, events, Boards and Automations; discover action types; search.
- write create and edit content, Boards and Automation drafts; explicitly enable or pause Automations.
- delete remove rows and events, move Boards to trash, or permanently delete Automations and their logs.
The most restrictive rule always wins, and workspace/table permissions still apply on top — the MCP server never bypasses your existing access controls.
MCP Automation creates and edits are saved paused. Enable an Automation explicitly only after reviewing it: future triggers may send messages, change records, or consume credits. Stored credential fields are omitted from MCP reads; configure credentials and webhook URLs in Fruitask. Board updates require the latest updatedAt value so a stale request cannot overwrite newer work.
Capabilities & current limits
Use list_files to search your account uploads, then get_file for a download link. Private links are refreshed through the original provider; Google Drive links require Google sign-in. These tools return file metadata and URLs, not extracted contents.
File uploads use your account storage and configured provider. Private by default; public URLs can be opened by anyone. Maximum 10 MiB per file. Uploading does not attach the file to a table.
API-key scopes do not grant extra access: workspace, table, note and calendar permissions still apply. Restricted tables and hidden rows stay protected.
Row tools support native Fruitask tables. External-database rows require the table editor. Row writes apply configured defaults and can trigger existing Automations.
Notes support checklist blocks with checked state. Calendar reads return recurring-series definitions, not expanded occurrences. Edit recurring or synchronized events in Calendar, and manage room reservations in Virtual Office.
Automation creates and edits are paused drafts; enabling is a separate action. Stored credentials are omitted from reads. Board and Automation edits require the latest updatedAt version.
Compatible clients
Use Streamable HTTP with API-key authentication. Legacy SSE clients can continue using the /sse endpoint.
Fruitask logo
Adding Fruitask as a connector or integration on another platform? Download the official Fruitask MCP icon to use as the connection's logo.
Or paste the image URL directly where the platform asks for a logo URL:
https://fruitask.com/brand-logo/fruitask-mcp.pngReady to connect your AI?
Create a scoped API key and point your MCP client at the endpoint above.
