Hosted MCP server/Productivity

FileNest WorkTools MCP server

Hosted at filenest-pages.pages.dev·Streamable HTTP

FileNest WorkTools provides read-only discovery of browser-based file utilities so an agent can identify the right task for batch renaming, image processing, PDF work or other everyday file jobs. The endpoint at https://filenest-pages.pages.dev/mcp exposes two tools: list_filenest_tasks returns published tasks, fit boundaries and canonical tool URLs, and get_filenest_task returns one task with its restrictions. It never reads or processes user files; users complete file selection and processing on the FileNest website.

filenest-pages.pages.dev Streamable HTTP No authentication Server not checked yet Reviewed 2026-11-16
About

Where it fits

People who want an assistant to point them to the right browser-based file utility.

  • List supported FileNest tasks with list_filenest_tasks.
  • Look up one task and its fit restrictions with get_filenest_task.
  • Find a utility for batch file renaming or image processing.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds FileNest WorkTools as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http filenest-worktools https://filenest-pages.pages.dev/mcp --scope project
  2. 02

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://filenest-pages.pages.dev/mcp
Host
filenest-pages.pages.dev · /mcp
Transport
Streamable HTTP
Authentication
No authentication
Server name
filenest-worktools
Listing type
Community or directory listing

The installer uses the server name filenest-worktools. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that filenest-worktools appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: List supported FileNest tasks with list_filenest_tasks. Check the result before you give the server more access.

  3. 3
    Check permissions.

    The provider documents no credential for this endpoint, so there is no scope or token to review. Remove the server when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The server connects but no tools appear. Confirm the URL and transport, then restart the client.
  • The first tool call times out. Try a smaller request and check the provider's status or rate limits.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

FileNest WorkTools documentationhttps://filenest-pages.pages.dev/en