Западный рынок: конкуренты и GTM без Telegram

English

Trip2G turns your Markdown, docs, and team knowledge into a distributed MCP memory network for AI agents.

Альтернативы:

Make your docs agent-readable.

Connect your knowledge to Claude and Cursor.

A federated knowledge layer for Claude, Cursor, Codex, and every MCP-aware agent.

Not another chatbot. A knowledge network your agents can actually use.

Russian working translation

Trip2G превращает markdown, документацию и командные знания в распределённую MCP-память для AI-агентов.

1. Agent memory infrastructure

2. RAG frameworks and knowledge pipelines

3. Enterprise knowledge search and internal AI

4. Docs-to-agent / support bots / website RAG

5. PKM / second brain

6. MCP ecosystem and tool marketplaces

Не вести с Telegram

Telegram оставить как optional adapter. Для Western market в hero лучше использовать:

• Obsidian;
• GitHub/Markdown docs;
• Notion;
• Google Drive / Google Docs;
• Slack;
• Discord;
• Linear / Jira;
• Readwise;
• Web/docs crawler;
• MCP clients: Claude Desktop, Claude Code, Cursor, Codex, Windsurf, GitHub Copilot.

Wedge 1: GitHub/docs → MCP docs server

Best first developer wedge.

Hero:

Make your docs agent-readable.

Subheadline:

Connect your GitHub docs folder and give Cursor, Claude Code, and MCP clients grounded access to your real documentation.

Why strong:

• Developers already feel Cursor/Claude hallucinate APIs.
• Docs are often Markdown already.
• Easy public demos with open-source docs.
• Clear distribution through GitHub, HN, DevRel, MCP directories.

Killer demo:

User in Cursor: “Implement OAuth refresh using this SDK.”
Cursor calls Trip2G MCP:
- search("OAuth refresh token SDK")
- note_html("docs/auth/oauth.md")
- similar(...)
Then writes grounded code.

CTA:

Create free docs MCP server.

Paid expansion:

• more docs repos;
• private docs;
• custom domain;
• usage analytics;
• hosted sync;
• premium support;
• docs QA automation.

Wedge 2: Obsidian → Claude/Cursor memory

Hero:

Talk to your Obsidian vault from Claude.

Subheadline:

Trip2G turns your vault into a safe MCP server for Claude, Cursor, and other AI agents.

Why strong:

• Obsidian users understand local-first Markdown.
• They have real notes.
• They like plugins and technical workflows.
• Good early adopters for “knowledge network”.

CTA:

Connect first vault free.

Paid expansion:

• multiple vaults;
• private endpoint;
• hosted sync;
• public/private knowledge split;
• web publishing;
• automation/webhooks.

Wedge 3: Notion / Drive → team knowledge hub

Hero:

One MCP endpoint for your team knowledge.

Subheadline:

Expose selected Notion pages, Drive folders, docs and decisions as a secure MCP knowledge base for Claude, Cursor and team agents.

Why strong:

• Small teams already have knowledge scattered across SaaS.
• Glean is too enterprise/heavy.
• Notion AI is locked inside Notion.

CTA:

Connect one source free.

Paid expansion:

• multiple sources;
• teams/access control;
• scheduled refresh;
• Slack/Discord connectors;
• private hosted hub.

Wedge 4: Slack/Discord archive → answer engine

Hero:

Your community has already answered this. Let agents find it.

Subheadline:

Turn Slack or Discord discussions into curated, AI-queryable knowledge for support, onboarding, and docs.

Why strong:

• Western communities use Slack/Discord more than Telegram.
• Repeated questions are an obvious pain.
• Can generate FAQ/digests from archive.

CTA:

Turn one channel into an AI FAQ.

Paid expansion:

• hosted archive index;
• scheduled refresh;
• moderation workflows;
• community support bot;
• private/public access.

Wedge 5: Safe content backend for AI agents

Hero:

A safe content backend for AI agents.

Subheadline:

Versioned Markdown, scoped tokens, webhooks, cron, MCP tools and human review.

Why strong:

• Agent builders need safe writes, not just vector DB.
• Trip2G webhooks/cron/scoped tokens are rare and valuable.

Messaging:

• trigger agents when notes change;
• schedule recurring agent jobs;
• prevent infinite loops with depth limits;
• let agents write safely with expected hashes;
• use MCP for retrieval.

CTA:

Build your first agent workflow.

Paid expansion:

• hosted bots;
• custom adapters;
• workflow templates;
• high automation limits;
• support.

Highest priority

• Hacker News: Show HN / technical essays.
• r/ObsidianMD.
• Obsidian Forum / Discord.
• Cursor community/forum.
• Claude / Claude Code communities.
• Anthropic MCP discussions.
• MCP server directories: Smithery, Glama, PulseMCP-like directories.
• GitHub open-source projects with Markdown docs.
• DevTools Twitter/X.
• AI Engineer / Latent Space communities.
• LangChain / LlamaIndex Discords.

Medium priority

• r/Notion.
• Notion consultants.
• Indie Hackers.
• Product Hunt after demos.
• r/selfhosted.
• r/LocalLLaMA.
• r/AI_Agents.
• n8n / Make / Zapier communities.
• DevRel communities.
• Discord admin/community-builder groups.

Lower priority initially

• generic SaaS communities;
• generic productivity communities;
• enterprise KM communities;
• SEO/content marketing groups.

Reason: Trip2G needs technical/agent-aware early adopters first.

Week 1

Ship 2 focused landing pages:

1. /docs-to-mcp
2. /obsidian-mcp

Create public demos:

• one open-source docs MCP endpoint;
• one Obsidian/demo vault MCP endpoint;
• one webhook AI workflow demo.

Create 3 short videos/GIFs:

• Claude asks Obsidian vault;
• Cursor uses docs MCP;
• Webhook AI edits note safely.

Week 2

Outreach:

• 20 Obsidian users;
• 20 OSS maintainers;
• 20 DevRel/API startups.

Submit to MCP directories.

Post in MCP/Claude/Cursor communities.

Week 3

Run white-glove onboarding.

Publish technical essay:

Your docs need an MCP server.

Alternative essays:

• “Knowledge bases are becoming APIs for agents.”
• “RAG is not enough: agents need instructions, permissions, and safe writes.”
• “Markdown is the shared interface between humans and AI agents.”

Week 4

Double down on highest activation segment.

Add paid expansion prompt:

• second source;
• private/team access;
• webhooks/cron;
• hosted sync;
• custom adapter.

Collect 3 case studies.

Open-source maintainer

Hey — I noticed your docs are Markdown-heavy and users likely ask Cursor/Claude about your API.

I made a small MCP endpoint concept that lets Claude/Cursor search and read your docs directly instead of guessing.

Would it be useful if your README had: “Use these docs in Cursor/Claude via MCP”?

Happy to set up the first version free.

Obsidian user

I’m testing a tool that turns an Obsidian vault into an MCP server for Claude/Cursor.

The idea: keep writing in Obsidian, but let your AI assistant search and read your notes safely instead of copy-pasting.

Looking for 10 power users to try it free and tell me what breaks.

DevRel/API startup

A lot of your users are probably coding with Cursor/Claude now. The problem is those agents hallucinate APIs unless your docs are available as tools.

Trip2G can expose your docs as an MCP server with search, section retrieval, similar docs, and usage instructions.

Want a quick demo with your actual docs?

AI automation agency

We’re building a safe content backend for AI agents: versioned Markdown, scoped temporary tokens, webhooks, cron jobs, and MCP retrieval.

Useful when agents need to read/write client knowledge without getting full workspace access or overwriting data.

Want to try it on one client workflow?

Free

• 1 source.
• Hosted MCP endpoint.
• Basic search/read tools.
• Public or personal private endpoint.

Pro

• Multiple sources.
• Private sources.
• Larger index.
• Custom instructions.
• Webhooks/cron.
• More frequent sync.
• Priority indexing.

Team

• Team permissions.
• Scoped source access.
• Audit/version history.
• Slack/Discord/Drive/Notion connectors.
• Shared MCP endpoints.
• Admin controls.

Builder/API

• Agent write access.
• Scoped temporary tokens.
• Webhook workflows.
• Cron jobs.
• Higher automation limits.
• Custom domains/endpoints.

Не начинать с

• distributed knowledge base protocol;
• federated knowledge network;
• content infrastructure;
• programmable platform.

Это точные, но слишком абстрактные фразы для acquisition.

Начинать с

• Make your docs agent-readable.
• Turn your Obsidian vault into Claude/Cursor memory.
• Hosted MCP for your knowledge base.
• Safe content backend for AI agents.
• Connect Notion/Drive/docs to Claude via MCP.

Потом объяснять архитектуру

• MCP tools;
• vector search;
• note_html;
• similar;
• instructions;
• scoped tokens;
• webhooks/cron;
• depth protection;
• versioning;
• first source free;
• paid expansion.