Tycana

io.github.tycanaPublished by GitHub account tycanav1.0.0Updated Oct 24, 2026

Gives your AI assistant persistent memory and intelligence about your work patterns.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Tycana is a remote MCP server that gives an AI assistant persistent memory and insight into your work patterns.

What you can do
Provides the assistant with persistent memory that carries across sessions, according to the provider's description. Offers intelligence about your work patterns, so the assistant can draw on how you work. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Worth considering when you want an assistant that remembers context over time and understands your working habits, rather than starting fresh each session.
Requirements
A remote MCP endpoint at app.tycana.com over streamable HTTP; no packages, environment variables or headers are declared. The manifest declares no authentication, but an account on the provider's service may still be needed.
Before you install
The server is described as holding persistent memory about your work patterns, so consider what work data you are willing to share with a third-party service. No tools, authentication or data-handling details are documented in the supplied material.

Installation

In SourceWeft

  1. Open Tycana in the dashboard and add it to a workspace.
  2. 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/io.github.tycana%2Ftycana/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "tycana": {
      "type": "http",
      "url": "https://app.tycana.com/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

28% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.