Glossary term

What is full read-write access?

Full read-write access means a connection can both read data and write it back, creating and updating records the same way a person using the app could. A read-only connection can view information but cannot change it. Full read-write adds the ability to create and update, so the tool can act, not just report.

Why does full read-write access matter?

Full read-write access matters because reading alone cannot finish work. A read-only connection lets Claude summarize a record or answer a question about it. Full read-write lets Claude create the record, update its fields, and log the next step, so the work actually lands in the tool instead of being copied over by hand.

This is the difference between a connection you read from and one you work in. It is also why scope is described carefully: full read-write still authenticates as your own account, so it never grants more access than your login already has. For a deeper treatment of the two scopes, see read-and-write access.

How does full read-write access relate to Claude connectors?

Full read-write access relates to Claude connectors because a connector is what exposes both read tools and write tools to Claude over MCP. Read tools let Claude fetch data, write tools let it create and update records. A connector with full read-write wires up both sides for your specific tool.

Many directory connectors expose mostly read tools, so Claude can see your data but not change much. A custom connector can add the write tools that matter for your workflow, including writing to the custom fields a standard connector skips. Browse full read-write connectors to see what this looks like per tool.

What is an example of full read-write access?

An example of full read-write access is a CRM connector that not only reads a deal but also updates its stage, edits its custom fields, and logs a follow-up activity. A read-only version could describe the deal. The full read-write version lets Claude advance it inside the CRM in one step.

In that example, create and update actions run inside a conversation you start, while a destructive action like deleting the deal stays gated behind a confirmation you approve. That keeps full read-write useful for everyday work without handing over risky actions. For the full picture of how custom connectors are built and scoped, read the complete guide to custom Claude connectors.

Related terms

Read-and-write access: The broader pairing of reading data and writing it back, and how the two scopes differ.
Custom connector: A built-to-order MCP connector for a specific tool, where full read-write is configured.
MCP: The Model Context Protocol that a connector uses to expose read and write tools to Claude.

Frequently asked questions

What is full read-write access in simple terms?

Full read-write access means a connection can do everything a person could do in an app: read records and also create and update them. A read-only connection can look but not change anything. Full read-write lets Claude move work forward inside the tool, not just summarize it.

Is full read-write access the same as admin access?

No. Full read-write describes the type of actions allowed (reading plus creating and updating), not the level of permission. A connector authenticates as your own account and inherits its permissions, so it never reaches more than your login already can. A non-admin keeps non-admin scope even with full read-write.

Does full read-write let Claude delete or send things automatically?

Not without a check. Create and update actions flow freely inside a conversation you start. Destructive or outbound actions, like deleting a record or sending an email, are gated behind a human-in-the-loop confirmation you approve. Full read-write covers the write capability while keeping risky actions behind a step you control.

How is full read-write access enabled for a tool?

Full read-write is enabled through a connector that exposes both read tools and write tools over MCP and authenticates as your account. For tools without a deep off-the-shelf option, a custom connector maps your data and write actions so Claude can create and update records, not only read them.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us