What is MCP?MCP (Model Context Protocol) is an open standard that allows AI assistants to securely connect to external data sources. With this connector, any MCP-compatible AI can read and write data in your Nixa workspace.
Example ConversationsQuerying Data "Show me my recent contacts in Nixa" "What tasks are due this week?" "Summarize my sales pipeline" Creating Records "Add a new contact named John Smith with email john@example.com" "Create a task to follow up with Acme Corp next Monday" Updating Data "Mark the 'Website Redesign' task as complete" "Update the contact email for Jane Doe" Building Presentations "Build a ten-slide project update with live widgets and speaker notes" "Clean up this deck, fix overlaps, and fit overflowing text" "Export the current presentation as a PDF"
Security & Permissions- OAuth 2.1 — Industry-standard secure authentication
- Scoped Access — Claude only accesses what you explicitly authorize
- Permission Inheritance — Claude has the same permissions as the authorizing user
- Audit Trail — All MCP operations are logged
- Revocable — Disconnect Claude at any time from settings
Supported Operations- List Entities — View your data structure
- View Records — Read data from any entity
- Create Records — Add new records
- Update Records — Modify existing records
- Delete Records — Remove records (requires explicit scope)
- Build Presentations — Read, analyze, create, clean up, update, and export native Slides decks
PrivacyYour data is processed according to Nixa's privacy policy. MCP requests are logged for security auditing. Information returned to an external assistant may be processed and retained under that provider's terms.
Event subscriptionsCompatible hosts can subscribe to selected record creation, relevant record field changes, and human messages in selected record discussions. This requires separate event consent and existing read permissions. Callback verification and signing protect delivery. Only identifiers and permitted change metadata are sent; record values, message text and attachments are excluded. Imports, restored records, system messages and email activity are excluded. Subscriptions expire within one day unless refreshed, can be stopped by the host, and stop when access is revoked. Events and delivery state are retained for up to seven days; inactive subscription metadata is removed within eight days. Provider acceptance acknowledges receipt rather than completed assistant work. Host availability and connection discovery are required; installing Nixa alone does not activate monitoring.
Browser Site ToolsSupporting browsers can discover Nixa page actions and existing MCP business operations through WebMCP while you are signed in. Browser access requires the installed MCP app, current page permissions, and your consent for the page session. It does not require a remote MCP OAuth connection. Shared page actions can change views and filters, open permitted pages, and save UI preferences. Business reads use your existing app and record permissions; writes require separate approval of the exact operation and arguments through the existing confirmation service. Returned data may be processed by the external assistant provider under its terms. Consent expires after ten minutes and can be revoked from the in-app access notice; revocation cannot undo an operation already started. The server stores only hashed session bindings and expiry for the page grant. Existing domain retry safeguards apply; no new durable receipt store is introduced. Page consent, operation approvals, and page-memory retry receipts are not exported with workspace blueprints.
