Skip to main content
Keep files for later use by your MCP client in persistent, account-specific storage. Endpoint: https://<NEURON_HOST>/MCP/Files. Use the host supplied by your provider.

​
What you need

You need file resource permissions to list or read files, and the corresponding tool privileges to create or change them. File URIs belong to the account storage and are not shared download links.

​
Scopes and privileges

The server advertises these OAuth scopes:
Request the categories you need. The provider must also grant the corresponding role privileges; see Scopes and permissions. For the tables below, prepend OAUTH.Scope.MCP.Files. to each suffix. When a row lists multiple privileges, all are required. For example, OAUTH.Scope.MCP.Files.Tools.Append is a complete privilege name.

​
Tools

Select a tool name for its complete arguments, defaults, and return values in the original reference. Discover tools in your client to check what your session can use.

​
Use this server

List resources and read a returned URI to inspect an existing file. To create a text file, call CreateTextFile with LocalFileName, Content, and AppendCrLf. It returns a resource URI and replaces an existing file with the same name. Binary tools take Base64 content. File names must stay within the storage area: do not use .. or a leading path separator. For EditFile, set Sensitive to true when editing requires a protected window.

​
Resources and prompts

Each resource represents a stored file. Subscriptions report file changes. No custom prompts are documented. See the original File Storage reference for complete schemas and response types, or return to MCP servers.