Contact
We're a small team. We don't have a support ticketing system or a chatbot, just email. We aim to reply within two business days.
Report a bug
If a tool is giving wrong results, crashing, or behaving unexpectedly, let us know. Include the tool name, what you expected, and what actually happened.
bugs@toolsnest.ioSuggest a tool or feature
We're always looking for useful tools to add. If there's something you keep needing to do in the browser and can't find a clean free tool for it, tell us.
ideas@toolsnest.ioBlog or content feedback
Found an error in one of our articles? Spotted outdated SEO advice? We update posts regularly, your correction is genuinely appreciated.
content@toolsnest.ioEverything else
Privacy questions, partnership enquiries, legal notices, or anything that doesn't fit the above, use the general inbox.
hello@toolsnest.ioRequest MCP access
Want an AI agent to call ToolsNest tools directly? You need a bearer token for the MCP server first.
See how below ↓Requesting MCP access
ToolsNest runs a remote MCP server at https://toolsnest.io/mcp that lets a compatible AI client call our SEO and text tools directly. It is not open to anonymous traffic, every request needs a bearer token. This is the single place we document how to get one, the MCP documentation page and server discovery card both point here.
- What it isA bearer token is a secret string your MCP client sends with every request to prove it is allowed to call ToolsNest tools over the Model Context Protocol.
- Why it is requiredThe MCP endpoint runs real work on our servers on every call (fetching a page, running an audit) rather than serving a cached response. A token keeps usage attributable to one client and inside the rate limit, so no single client can use up the service for everyone else.
- How to request oneEmail hello@toolsnest.io with the subject line "MCP access". There is no self-serve signup yet, requests are handled by a person.
- What to includeThe name of the client or agent you are connecting (Claude Desktop, a custom agent, etc.), a one or two line description of what you are building, and the email address you want the token sent to.
- How you receive itWe reply by email with your token and the exact configuration block to paste into your client. We typically reply within one to two business days, the same as any other request.
Response time: We typically reply within 1, 2 business days. We are a small independent project, not a funded company, so please be patient.
No spam, ever:Your email address will only be used to reply to your specific message. We don't add you to any mailing list.