List Dosya MCP tools and resources
Inspect Dosya’s nine read-only MCP tools, their schemas and scope needs, and understand why the server currently publishes no MCP resources.
Last reviewed
Dosya currently publishes MCP tools, not MCP resource objects. The protected resource URL https://mcp.dosya.dev/mcp identifies the OAuth audience; it does not imply that resources/list contains files.

Steps
- Open the connected Dosya server in the MCP client and refresh its capabilities. Confirm the server identifies itself as dosya and the connection is authenticated with required
files.readaccess. - Check for the core navigation tools:
list_workspaces,list_folder,search_files, andget_file_info.list_folderaccepts an omittedfolder_idfor the top level and an optionalworkspace_idreturned bylist_workspaces. - Check the content tools:
read_fileandget_download_link.read_filereturns bounded text with a continuation cursor;get_download_linkcreates a new five-minute bearer URL and is therefore read-only but not idempotent. - Check
get_account_info. It is the only current tool requiring optionalaccount.read; a client may open an OAuth scope prompt if that permission was not granted initially. - Check the research adapters
searchandfetch. They expose name search and document text in the shapes required by research clients; they do not add write capability beyondsearch_filesandread_file. - Inspect the annotations and resource view. All nine tools declare
readOnlyHint: trueanddestructiveHint: false; a blank or unsupported MCP resources view is expected because the server registers no resources.
Listing defaults are bounded. list_folder returns 25 combined entries by default and accepts at most 100. search_files pages folders and files independently, so its default is up to 25 folders plus 25 files and its maximum is 100 folders plus 100 files.

Expected result
The client displays nine Dosya tools with input schemas and read-only annotations. No mutation tool appears, and the absence of MCP resource objects is recognized as the current server design rather than a connection failure.
A tool is missing. Refresh the server definition or reconnect the client. If only get_account_info fails, grant See your plan and storage instead of replacing the whole connection blindly.
Files do not appear under Resources. Use list_folder or search_files; Dosya files are returned through tools in this release.
Related guides
Was this helpful?
Loading helpfulness results…
Voting saves a necessary ballot cookie for up to 180 days so you can change your answer.
Questions and replies
Ask about the steps in this guide. Questions are reviewed before publication.
Keep account details, credentials and private files out of public questions. Use private support for those.
Loading questions…
Sign in to your Dosya account to ask a question.