thinqOS
com.thinqosPublished by thinqos.comOfficial publisherv1.16.1Updated Oct 24, 2026
Memory with judgment: decides which of your context reaches each task, per identity.
Overview
Gives an assistant a per-identity memory that selects which stored context is relevant to each task.
- What you can do
- thinqOS is a hosted memory service exposed as a remote MCP endpoint. According to its description, it provides memory with judgment: it decides which of your context reaches each task, scoped per identity. No tool list is published, so the specific operations the assistant can call are not documented in the supplied material.
- When to use it
- Consider it when you want an assistant to carry context across sessions and have that context filtered per task and per identity, rather than dumping everything into every prompt. It suits users who are comfortable storing context in a hosted third-party service and authenticating with OAuth. Because no tools are listed, evaluate it only if you can confirm its behavior another way.
- Requirements
- A remote MCP endpoint at over streamable HTTP. OAuth authentication is required. No packages, environment variables, or headers are declared. Network access to the provider's hosted service is needed.
Installation
In SourceWeft
- Open thinqOS in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.thinqos%2Fmind/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"thinqos": {
"type": "http",
"url": "https://app.thinqos.com/mcp"
}
}
}Tools
0Version history
1- v1.16.1LatestSep 23, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.