# ToolsPad [Health: Active]

**Category:** 🏢 Workplace & Productivity  
**Repository:** https://toolspad.com/mcp?utm_source=allmcps&utm_medium=referral&utm_campaign=aidm&utm_id=aidm_organic_v1&utm_content=allmcps_workspace_001  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/toolspad

## Description
Connect an AI assistant to one approved ToolsPad workspace to work with contacts, notes, tasks, forms and appointments. The remote MCP server uses OAuth and Streamable HTTP. Choose read-only or read-and-write access, and revoke the connection in ToolsPad settings.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: medium). Install path inferred — verify against the README before running it. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "toolspad": {
    "url": "https://toolspad.com/mcp?utm_source=allmcps&utm_medium=referral&utm_campaign=aidm&utm_id=aidm_organic_v1&utm_content=allmcps_workspace_001"
  }
}
```

## Documentation

## What ToolsPad MCP server does

ToolsPad MCP server gives an AI assistant access to selected data and work items in a ToolsPad workspace. Its available areas are contacts, notes, tasks, forms, and appointments. The connection is limited to one approved workspace, which helps keep the assistant’s scope tied to a specific ToolsPad environment.

The server is a fit for workplace and productivity workflows where an assistant needs to retrieve information or make changes in ToolsPad. Access can be configured as read-only when the assistant should only inspect workspace content, or as read-and-write when it also needs to update supported records.

## How it works

ToolsPad exposes the connection remotely rather than requiring a local server process. Communication uses the Streamable HTTP MCP transport, while OAuth handles authorization between the AI client and ToolsPad.

During connection, the user approves access to a ToolsPad workspace and selects the permitted access level. After authorization, the MCP client can use the available ToolsPad capabilities within that scope. The connection remains associated with the approved workspace until it is revoked in ToolsPad settings.

## Setup and configuration

Add ToolsPad as a remote MCP server in an MCP-compatible client that supports Streamable HTTP and OAuth. Complete the OAuth authorization flow, choose the ToolsPad workspace to connect, and select either read-only or read-and-write permissions.

No local installation or environment variables are needed for the remote connection. To remove access later, revoke the connection from ToolsPad settings.

## Tools and capabilities

ToolsPad provides access to five workplace data areas:

- Contacts
- Notes
- Tasks
- Forms
- Appointments

The selected permission mode determines whether the assistant can only read these areas or can also write changes. The connection is scoped to one approved workspace rather than exposing multiple ToolsPad workspaces through a single authorization.

## Limitations and notes

Workspace scope and permission mode are central to the connection. An assistant connected in read-only mode cannot use write access, while read-and-write mode grants broader control over the supported ToolsPad areas.

The server relies on the MCP client’s support for remote Streamable HTTP connections and OAuth. Revoking the connection in ToolsPad settings removes the authorization for that client.

_Full upstream README: https://allmcps.com/mcp/toolspad/readme_