GrowthKit Revenue Intelligence
Sales intelligence for B2B SMEs — lead scoring, ICP fit, CRM enrichment & writeback.
От сообщества: Добавлен пользователем или импортирован; проверьте владельца перед подключениемРаботаетБез входаГлобальныйБесплатноМожет изменять данные
Что умеет
- SearchMemory: Search long-term memory using semantic similarity. ALWAYS SEARCH BEFORE ANSWERING marketing/strategy questions. Use short, specific keywords as queries. Available chapters: icp, strategy
- ListMemories: List stored memories in stored order with pagination. Unlike searchMemory (semantic relevance ranking), use this to browse, enumerate, or audit a chapter — not to find the most relevant
- CountMemories: Return only counts, not content — use for overview/sizing (e.g. 'how many competitor memories exist?') before deciding whether to list or search. Optionally filter by chapter via metada
Какие данные видит
Нужен ли аккаунт
Не нужен: сервер работает без входа
Sales intelligence for B2B SMEs — lead scoring, ICP fit, CRM enrichment & writeback.
Список инструментов сервера (15)
Технические названия из tools/list. Нужны только разработчикам.
| searchMemory | Search long-term memory using semantic similarity. ALWAYS SEARCH BEFORE ANSWERING marketing/strategy questions. Use short, specific keywords as queries. Available chapters: icp, strategy, campaigns, analytics, brand, competitors, learnings, general, pipeline, signals, playbook. TAG FILTERING: Memories are auto-tagged. Use metadata_filter with tags key to filter (e.g. metadata_filter: { chapter: 'campaigns', tags: 'linkedin' }). · Demo |
| listMemories | List stored memories in stored order with pagination. Unlike searchMemory (semantic relevance ranking), use this to browse, enumerate, or audit a chapter — not to find the most relevant memory for a question. Filter by chapter via metadata_filter.chapter. · Demo |
| countMemories | Return only counts, not content — use for overview/sizing (e.g. 'how many competitor memories exist?') before deciding whether to list or search. Optionally filter by chapter via metadata_filter.chapter. For a per-chapter breakdown in one call, prefer getChapterOverview. · Demo |
| getChapterOverview | Get memory count per chapter. Use as FIRST STEP in new conversations or reviews. · Demo |
| listDocuments | List stored documents with optional filtering by category or chapter. · Demo |
| getDocument | Get a specific document with fresh download URL and linked insights. · Demo |
| listReminders | List reminders, ordered by remind_at ascending. By default returns only pending reminders; pass status=sent|cancelled|all to widen. Optionally scope to one task via task_id. Returns each reminder's id, title, remind_at, and status. · Demo |
| getHistory | Get the version history of a specific memory. Shows all previous versions with timestamps and who made changes. · Demo |
| listDeleted | List recently deleted memories that can be restored. Shows content preview and deletion info. · Demo |
| listTeam | List all team members (token holders) for your account. Shows display names, roles, and identifies which token is yours. · Demo |
| listCampaigns | List campaigns for the current user, optionally filtered by status. Returns campaign metadata plus per-stage lead counts. · Demo |
| getCampaign | Get a single campaign with full briefing details and lead-stage counts. · Demo |
| getCampaignLeadFields | Discover which fields are actually used in a campaign's leads. Returns standard columns with non-null values PLUS all metadata (custom) keys with usage counts and sample values. ALWAYS call this BEFORE asking the user about lead structure or before adding new custom fields — it tells you what's already established for this list. · Demo |
| listCampaignLeads | List leads in a campaign, optionally filtered by lifecycle_stage or enrichment_status. Returns up to 100 per call. · Demo |
| getWorkingMemory | Retrieve the current state for a (kind, key) in the current session. Returns null if not set. Use this when you need to merge into existing state or verify what's stored. NOTE: Active working memory entries are ALSO automatically injected into the system prompt by Build Messages — you usually don't need to call this manually. Only call when you need a specific record's full state on-demand. · Demo |