# Toolcape + Onebase

Toolcape connects a company’s existing AI to its systems through one MCP entry point, with account connections, group and individual permissions, and audit logs. This documentation describes a product prototype; it is not evidence that a live server or account is connected.

## The connection
Onebase: The company’s tailored workspace for business processes such as customers, sales and inventory.
MCP server · connected through Toolcape
Provider sign-in (OAuth). Confirm whether the configured connection acts as the user or uses application permissions.

## Typical actions
- Read: Inspect the connected workspace’s available information
Uses the Onebase MCP server as the signed-in user. Available business actions depend on this customer’s installation; inspect them before granting access.

## Setup
1. IT verifies the MCP server address, provider and supported sign-in method.
2. Provider sign-in (OAuth). Confirm whether the configured connection acts as the user or uses application permissions.
3. Make the service available in Toolcape. Set Everyone, group and individual rules for the actions actually needed. Adding a service does not grant access.
4. Connect the approved AI client to the actual Toolcape MCP address and sign in. Start with a harmless read-only task and check the audit log.

## Permissions
For personal delegated access, the provider account, approved app scopes and Toolcape rules must all permit the action. Shared accounts and application permissions may have other limits. Toolcape combines Everyone and group grants; a personal exception replaces inherited access for that service. Reading can disclose confidential information. Sharing, sending and deletion need separate consideration.

## Calling an operation
First discover which tools the connected Toolcape server actually exposes. If it offers search → describe → execute, find the relevant operation, inspect its input schema and permissions, then call it with validated inputs. Tool names vary by server; do not invent names, arguments, URLs or successful outcomes. Without connected tools, give setup guidance instead of claiming to perform actions.

## Operation reference
Catalog snapshot: 16 September 2026. Verify the current schema before calling.
- foundationStatus — Read workspace status
  MCP 
  
- onebaseSearch — Find customers, projects and tasks
  MCP 
  
- onebaseContext — Read context for selected work
  MCP 
  
- onebaseCreate — Create a shared task or activity
  MCP 
  
- onebaseCollaborations — Read shared collaboration context
  MCP 
  
- onebaseTranscript — Read an approved shared transcript
  MCP 
  
- onebaseTaskStatus — Change task status
  MCP 
  

## A useful first question
What information is available in our Onebase workspace?

## If it fails
Check the account, expired authorization, app approval, provider scopes and Toolcape permissions. Share only redacted errors with support. Never paste passwords, tokens or client secrets into an AI conversation.