RxLog DocsMCP
Connect external AI tools to RxLog over MCP using a scoped API token.
RxLog exposes an MCP server so external AI tools — such as Claude or other MCP-aware assistants — can reach your workspace data programmatically. The connection is authenticated with an API token, so the outside tool talks to RxLog with exactly the permissions you grant it and nothing more.
How the connection works
You connect a tool by creating an API token with the Access MCP Server permission and pointing the tool's MCP client at RxLog using that token. The tool then authenticates as your workspace on every request, scoped to what the token allows.
API tokens live under Settings → API Tokens.
The list shows each token's name, permissions, expiry, last-used date, and creation date. A token past its expiry shows Expired and stops working — create a new one to restore access.
Tokens are shown only once, when created. If you lose a token you cannot read it back — create a new one and update your tool's configuration.
Creating an MCP token
Click Create Token to open the dialog.
Fill in:
- Token Name. A descriptive label so you remember what the token is for.
- Token Expiration. How long the token stays valid. Expired tokens are removed automatically; choose Never Expires only when you must.
- Token Permissions. What the token can do. For an MCP connection, enable Access MCP server.
Follow least privilege: give each token only the permissions its tool needs, prefer a real expiry over Never Expires, rotate tokens regularly, and never put a token in a public repository or client-side code.