How do I install the Famulor Assistants History skill?

Run npx skillmds@latest add bekservice/famulor-assistants-history in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Famulor Assistants History safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Famulor Assistants History?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Famulor Assistants History free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Famulor Assistants History?

bekservice (@bekservice) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Famulor Assistants History by bekservice

Name: Famulor Assistants History
Rating: 4.2 (5 reviews)
Author: bekservice

Famulor Assistants History

Read Famulor assistant configurations, versions, catalogs, and omnichannel conversation history through the restricted Assistant & History MCP profile. Use for reviewing assistants or finding and summarizing call, messaging, or email history; never use it to change resources, send messages, place calls, run campaigns, manage telephony, or access billing.

bekservice Updated Sep 10, 2026

File contents

Famulor Assistants & Omnichannel History

Use the OAuth-secured Famulor MCP profile at:

https://app.famulor.io/mcp?profile=assistant-history

This marketplace profile is intentionally read-only. It exposes exactly 11 tools:

Tool	Use
`list_assistants`	List assistants visible in the authenticated workspace.
`get_assistant`	Read one assistant's configuration.
`list_assistant_versions`	List saved versions for an assistant.
`get_assistant_version`	Read one saved assistant version.
`list_prompt_templates`	List available prompt templates.
`get_languages`	List supported language options.
`get_models`	List models available to the workspace.
`get_voices`	List available voices.
`list_history`	Search unified call, messaging, and email history.
`get_call`	Read full details for one call returned by history.
`get_email_history_item`	Read the full email thread for one email history item.

Workflow

Confirm which authenticated Famulor workspace the user means when it is ambiguous.
Use a list_* tool to find the exact resource or history item instead of guessing an ID.
Use the matching get_* tool when the user needs full detail.
Summarize only the fields returned by the server and preserve the distinction between configured values and observed history.

list_history is the omnichannel overview. It may include voice calls, emails, and messaging conversations from connected channels such as Instagram or Messenger. Messaging entries can be previews rather than complete chat transcripts; never claim a full conversation unless the server actually returned it. Use get_call for call detail and get_email_history_item for an email thread.

Safety and access boundaries

Keep every request read-only. This profile cannot create, update, delete, send, call, launch, purchase, transfer, or configure anything.
Do not bypass the restricted profile when a user requests a write action. Explain that the installed marketplace integration supports Assistant & History review only.
Never infer access across workspaces. OAuth scopes, workspace membership, role, plan, retention, and server-side policy remain authoritative.
Treat transcripts, recordings, messages, emails, contacts, and customer context as personal data. Return only what is necessary for the request.
Use live tool schemas for arguments and availability; do not invent IDs, enum values, or fields.

---name: famulor-assistants-historydescription: Read Famulor assistant configurations, versions, catalogs, and omnichannel conversation history through the restricted Assistant & History MCP profile. Use for reviewing assistants or finding and summarizing call, messaging, or email history; never use it to change resources, send messages, place calls, run campaigns, manage telephony, or access billing.license: MIT---# Famulor Assistants & Omnichannel HistoryUse the OAuth-secured Famulor MCP profile at:```texthttps://app.famulor.io/mcp?profile=assistant-history```This marketplace profile is intentionally read-only. It exposes exactly 11 tools:| Tool | Use || --- | --- || `list_assistants` | List assistants visible in the authenticated workspace. || `get_assistant` | Read one assistant's configuration. || `list_assistant_versions` | List saved versions for an assistant. || `get_assistant_version` | Read one saved assistant version. || `list_prompt_templates` | List available prompt templates. || `get_languages` | List supported language options. || `get_models` | List models available to the workspace. || `get_voices` | List available voices. || `list_history` | Search unified call, messaging, and email history. || `get_call` | Read full details for one call returned by history. || `get_email_history_item` | Read the full email thread for one email history item. |## Workflow1. Confirm which authenticated Famulor workspace the user means when it is ambiguous.2. Use a `list_*` tool to find the exact resource or history item instead of guessing an ID.3. Use the matching `get_*` tool when the user needs full detail.4. Summarize only the fields returned by the server and preserve the distinction between configured values and observed history.`list_history` is the omnichannel overview. It may include voice calls, emails, and messaging conversations from connected channels such as Instagram or Messenger. Messaging entries can be previews rather than complete chat transcripts; never claim a full conversation unless the server actually returned it. Use `get_call` for call detail and `get_email_history_item` for an email thread.## Safety and access boundaries- Keep every request read-only. This profile cannot create, update, delete, send, call, launch, purchase, transfer, or configure anything.- Do not bypass the restricted profile when a user requests a write action. Explain that the installed marketplace integration supports Assistant & History review only.- Never infer access across workspaces. OAuth scopes, workspace membership, role, plan, retention, and server-side policy remain authoritative.- Treat transcripts, recordings, messages, emails, contacts, and customer context as personal data. Return only what is necessary for the request.- Use live tool schemas for arguments and availability; do not invent IDs, enum values, or fields.

Frequently asked questions