lnkz-mcp
LNKZ MCP is a portable conversation memory and handoff server: it saves/imports chats, lets you search, analyze, export, and share context, and manages secure cross-client handoffs.
Save and import conversations from ChatGPT, Claude, Gemini, LNKZ, Markdown, or plain text, with tags and dry-run support.
Retrieve, list, search, append to, export, and delete stored conversations.
Analyze conversations for decisions, open questions, action items, cited facts, and topics; find conflicts and near-duplicates.
Build conversation graphs and token-budgeted context packets from stored and connected sources.
Create, redeem, continue, revoke, and list expiring/use-limited handoff links; optionally redact secrets.
Discover downstream MCP publish targets and prepare payloads without sending them.
Search connected context sources such as LNKZ, Slack, Jira, Figma, documents, and federated MCP servers; list connector status.
View workspace statistics and audit events.
Searches configured Jira connectors as part of search_context, federating Jira content alongside LNKZ conversations and other sources in a single query.
Optional LLM provider for semantic_search and ask_conversations, enabling meaning-based ranking and grounded answers with citations while keeping conversation text on a self-hosted Ollama server.
Optional LLM provider for semantic_search and ask_conversations, enabling semantic ranking and grounded answers with citations; also supports OpenAI/ChatGPT conversation import and export formats.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@lnkz-mcp Search my recent conversations for duplicates"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Agentick | Federal Spaces demo
An analyst on one team prepares a disaster briefing. Before another team uses it, they want to know which records support the finding, what those records cover, and who approved the wording. Federal Spaces keeps the brief, its sources, and the review decisions together in one work item.
The Virginia example. The saved OpenFEMA response contains five county records for declaration 3631. Goochland, Caroline, Montgomery, York, and Bedford each have a row. All five rows carry the same declaration number. The brief can say those counties appear in this sample. Establishing the full extent of the disaster would require checking the full declaration and current designations.
View the presentation · Inspect the five source records
Walk through the handoff
Prepare the brief. As Operator, open the work item and select Prepare analyst brief. Compare the county names and declaration number with the attached snapshot, then select Submit for review.
Review the wording. Under Account → Acting as, choose Reviewer 1 and select Approve this handoff. The work item stays pending at 1 of 2. Switch to Reviewer 2, check that the wording stays within the sample, and approve to complete the handoff.
Check what the receiving team gets. Download Approval → Audit package → JSON. The file contains the source references, original draft, submitted wording, and both reviewers’ decisions. The verification command below checks that the text matches the recorded hashes.
Related MCP server: Concierge Core Kit
Run it locally
With Node 22 and Corepack:
git clone https://github.com/nsirivolu27/Agentick.AI.git
cd Agentick.AI
corepack pnpm install --frozen-lockfile
corepack pnpm build:workbench
corepack pnpm demo:openfemaOpen the work-item URL printed in the terminal. You can play all three roles without an account or API key. The demo uses a real OpenFEMA snapshot, a rule-based analyst, and an offline replay of Foundry reads.
After downloading the audit package, open another terminal in the repository and substitute the path to your file:
corepack pnpm audit:verify "C:\path\to\downloaded-audit.json"Available Tools
24 toolsanalyze_conversationAnalyze a conversationARead-only
Extracts decisions, open questions, action items, cited facts, and topics from one stored conversation without calling a model.
Inputs: conversationId (required).
append_messagesAppend messages to a conversationA
Adds new turns to an existing conversation, which is how a thread continued in a second client stays one thread.
Inputs: messages (required), conversationId (required).
audit_logRead the audit logCRead-only
Returns recent LNKZ events: saves, imports, handoff creation, redemption, rejection, and revocation.
Inputs: limit.
build_context_graphBuild the conversation graphARead-only
Builds a graph over the stored conversations: nodes for conversations, decisions, open questions and shared topics, and edges for lineage, shared subject matter, near duplicates and contradictions. Answers the questions search cannot: what this corpus knows, which decisions everything else leans on, and which conversations stand alone. Every edge carries the reason it exists.
Inputs: limit, maxTopics, conflictThreshold, duplicateThreshold, +1 more.
build_context_packetBuild a context packetARead-only
Assembles a token-budgeted brief from stored conversations and connected sources: decisions, open questions, action items, a recent excerpt, and any contradictions between chats. Use this instead of pasting a whole transcript.
Inputs: query, budgetTokens, conversationIds, includeExternal, +1 more.
continue_handoffContinue a handed-off conversationC
Redeems a handoff and stores the continuation as a new conversation in this client, linked back to the original so the chain stays walkable.
Inputs: token (required), messages (required), provider (required), app, +1 more.
create_handoffCreate conversation handoffA
Mints an expiring, use-limited bearer link that another person, device, or LLM client can redeem for portable context. Optionally redacts secrets before the packet leaves.
Inputs: conversationId (required), note, redact, maxUses, +2 more.
delete_conversationDelete conversationADestructiveIdempotent
Permanently removes a conversation, its messages, and its handoffs.
Inputs: id (required).
export_conversationExport a conversationARead-only
Writes a stored conversation back out in another client's format: a Markdown transcript, a Markdown brief with the decisions on top, a chat-completions message array, a ChatGPT-shaped export, a Claude-shaped export, a LNKZ packet, or plain text. Every format re-imports, so a conversation can leave LNKZ as easily as it arrived.
Inputs: conversationId (required), format.
find_conflictsFind contradicting decisionsARead-only
Compares decisions across recent conversations and reports pairs that appear to disagree. Heuristic: it surfaces candidates for review, it does not adjudicate them.
Inputs: limit, threshold.
find_duplicatesFind near-duplicate conversationsARead-only
Reports conversations whose transcripts overlap heavily, which happens whenever the same chat is relayed through more than one client.
Inputs: limit, threshold.
get_conversationGet conversationARead-only
Loads a stored conversation with its messages, lineage, extracted decisions, and a portable Markdown transcript.
Inputs: id (required).
import_conversationImport a chat from another clientC
Normalizes a ChatGPT, Claude, Gemini, LNKZ, Markdown, or plain-text transcript into portable conversations. Format is detected automatically unless one is given.
Inputs: payload (required), tags, dryRun, format.
list_connectorsList connector statusARead-only
Shows which context sources are configured and which are disabled, with the reason.
Inputs: no named parameters.
list_conversationsList conversationsARead-only
Lists stored conversations newest first, optionally filtered by provider, tag, or participant.
Inputs: tag, limit, offset, provider, +1 more.
list_handoffsList handoffsBRead-only
Shows issued handoffs with their expiry, remaining uses, audience, and revocation state. Tokens are never returned.
Inputs: conversationId.
list_publish_targetsList publish targetsARead-only
Connects to every configured downstream MCP server and lists the tools it exposes, marking which ones look like writes. Configure targets with LNKZ_MCP_TARGETS as name=url, optionally name=url|key. This is discovery only: it reads what is available and changes nothing.
Inputs: no named parameters.
prepare_publishPrepare a conversation for another systemARead-only
Maps a conversation onto a downstream MCP tool's input schema and returns the exact call that would be made, including which required fields it could not fill. It never sends anything. Review the payload, then make the call yourself with that server's own tool if you want it to happen.
Inputs: tool (required), target (required), conversationId (required), shape.
redeem_handoffRedeem conversation handoffC
Loads the portable packet behind an unexpired LNKZ handoff token, including the transcript and the extracted decisions and open questions.
Inputs: token (required).
revoke_handoffRevoke handoffBIdempotent
Immediately invalidates a handoff link that has already been shared.
Inputs: handoffId (required).
save_conversationSave portable conversationC
Stores a normalized conversation from any LLM client or device so it can be searched, packaged, or handed off.
Inputs: title (required), source (required), messages (required), id, +5 more.
search_contextSearch connected contextARead-only
Searches LNKZ conversations plus every configured connector (Slack, Jira, Figma, documentation feeds, and any federated MCP server) in one call, reporting per-source failures instead of hiding them.
Inputs: query (required), limit, sources, excludeSources.
search_conversationsSearch LNKZ conversationsARead-only
Full-text ranked search across saved chats by title, summary, participant, tag, or message content.
Inputs: query (required), limit.
workspace_statsWorkspace statisticsARead-only
Counts stored conversations and messages, the providers they came from, and active handoffs.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 24 tools
Most tools have clearly distinct purposes, but some close pairs exist such as save_conversation vs. import_conversation vs. append_messages, and search_conversations vs. search_context. Descriptions are detailed enough to disambiguate, though a couple of analytic/export tools could be confused at a glance.
The naming is predominantly consistent snake_case verb_noun (save_conversation, list_handoffs, build_context_graph). A few outliers like workspace_stats and audit_log are noun-first rather than verb-first, but the pattern is otherwise uniform and readable.
At 24 tools, the surface is on the heavy side and exceeds the typical 3-15 well-scoped range. Each tool appears to have a reason to exist, but the count feels more like a full platform API than a focused MCP server, making it borderline.
The tool set covers the full conversation lifecycle: save/import/get/list/delete/append/export, handoff creation/redemption/continuation/revocation, analytics, search across connectors, and audit logging. No major gaps are apparent for the stated purpose of managing portable conversations and handoffs.
Maintenance
Related MCP Connectors
Hosted MCP memory and agent control plane for durable conversations, jobs, and operations.
Query, browse, and automate OmegaAI workspaces from any MCP client. Streamable HTTP with OAuth 2.0.
Discover MCP servers and A2A agents; verify, message, post, follow, react, and receive webhooks.
A managed runtime for custom API integrations. Manage lines, endpoints, keys, logs and DLQ via MCP.
Related MCP Servers
AlicenseAqualityBmaintenanceEnables clients to interact with PipesHub data and functionality through MCP, including chat, search, record retrieval, directory browsing, sources, and agents.74,436 npm17Apache 2.0- AlicenseNot gradedqualityCmaintenanceEnables authorized clients to invoke tenant-aware conversational assistant tools and resources over MCP, including durable conversations, agent configuration, connector policies, and PostgreSQL-backed data.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables agents to discover rooms, read conversations, register, create rooms, post messages, and reply through MCP or HTTP with bearer-token authentication.MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to discover and connect over MQTT, list and invoke tools, and read resources in browser and Node.js environments.4 npmMIT