MCP server CRM: control Armiflow from your AI chat.

Yes. You describe the industry and location in the chat, such as tax advisers in Linz, and Armiflow starts the company search. The search uses Armiflow’s data sources such as OpenStreetMap or Google Places. Duplicates are merged automatically, and public authority protection remains active as usual.

Yes. Via the MCP server, you start Armiflow agents directly from Claude, for example for a search followed by analysis and drafting. The agents then work as usual in Armiflow and respect time limits. Automatic sending is off by default and needs its own password-confirmed approval in Armiflow.

Yes. Website reports from Armiflow can be retrieved via the MCP server CRM. Among other things, the reports score technology, GDPR, mobile, SEO, GEO and performance from 0 to 10 and are based on measured facts. This lets you discuss results directly in the chat, for example to prepare for a client meeting.

The MCP server gives your AI tool access to Drive, as far as the connection allows. This lets you work with files and documents without opening the Armiflow app, for example while you prepare a client meeting in the chat. You control which actions are allowed through the permissions per connection.

Yes. Via the MCP server, you can create social posts straight from the AI chat. For publishing on Facebook, Instagram, TikTok and YouTube, you use the Social Media Autopilot module, in review mode or fully automatic. This way a post is created right in the conversation without switching tools.

Yes. Appointments from Armiflow can be queried via AI chat, for example by asking what is coming up this week. Armiflow syncs bookings with Calendly, enters appointments in Google and Microsoft 365 calendars and creates Zoom, Teams or Meet links. A booking stops running follow-ups automatically.

MCP is an open standard supported by a growing number of AI applications, including Claude. Armiflow’s MCP server is therefore aimed at Claude, ChatGPT & co. Whether and how a particular tool offers MCP connections is decided by its provider. Check this in your AI tool’s documentation before setting it up.

No. The REST API in Basic and Pro is aimed at developers who connect Armiflow to their own software. The MCP server is designed for AI tools: you talk in the chat, and the AI tool calls the right functions. For systems such as HubSpot or Pipedrive, there are also ready-made CRM integrations.

Armiflow AI is the assistant built directly into the app and works with every function. You use the MCP server CRM if you prefer to stay in your usual AI tool, such as Claude, and control Armiflow from there. Both routes access the same data, so you simply choose the more convenient one.

Yes. Each connection gets its own permissions. For example, sales can search for companies and start agents, while others only see appointments. Roles and custom roles also apply in the account. Basic includes one user, Pro an unlimited number. Current package details are on the pricing page.

Because many teams already work with AI chats. An MCP server CRM brings your own customer data into that conversation instead of copying it over laboriously. This produces answers based on real leads, reports and appointments. For SMEs without their own IT department, it is a simple way to put AI to practical use in sales.

Yes. As soon as personal data such as contact names or email addresses ends up in the AI chat, the rules of the GDPR apply. So restrict connections to what is necessary and check the data processing agreement with your AI tool’s provider. Armiflow itself supports data access and erasure requests under Art. 15 and 17.

When copying, more data than necessary often ends up in the chat, and the information quickly goes out of date. Via the MCP server CRM, the AI tool accesses the approved functions in a targeted way and with current data. You save time, and the permissions per connection limit what the tool can see and do at all.

No. The connection runs via OAuth 2.1. You sign in to Armiflow and allow access, and Claude then receives its own access credentials instead of your password. This way you don’t reveal any credentials in the chat and can restrict the permissions of this connection precisely.

For companies, agencies and service providers who already work with AI tools such as Claude and want to use their sales data there. It is particularly handy for founders and small teams who do a lot in the chat. If you prefer to work directly in the app, use the Armiflow AI assistant instead.

Actions you trigger via AI chat run in Armiflow. Companies found are then in the CRM, agents you started keep working as usual, and social posts you created are in Social Media Autopilot. Your team therefore sees the results in the app, whether they come from the chat or the interface.

You use the MCP server with your own AI tool, such as Claude. Whether a paid subscription with the provider is required depends on its terms. Within the Armiflow app, you also have the Armiflow AI assistant available, without any external AI tool at all.

At Armiflow, permissions are granted per connection. This means you can run different connections with different permissions, such as one for company search and one for appointments. Which AI tools you use for this depends on whether they support MCP. Keep the number of connections as small as possible.

Zapier, Make and n8n connect systems through fixed workflows that you set up in advance. The MCP server CRM, by contrast, works in conversation: you ask, and the AI tool picks the right Armiflow function. Both approaches complement each other, as Armiflow also supports webhooks, Zapier, Make and n8n.

Write to support@armiflow.com. The team helps you connect Armiflow to your AI tool and decide which permissions make sense for your connection. You can also find the basics of the Model Context Protocol on the official website of the standard.