MULTI-APP TOOLKIT
Build with IONOS Hosting Services + n8n.io
- Multi-app
- One MCP session
- 8 actions
- 0 triggers
- Managed auth
MCP
One MCP session, both toolsets
One session gives your product or agent every IONOS Hosting Services and n8n.io tool at once — connect once, list tools, and call them like any single-app session.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "ionos_hosting_services,n8n_io",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// One list, both toolsets: IONOS Hosting Services and n8n.io tools arrive
// together, each keyed by its own app's slug.
// e.g. run Create DNS Records:
const result = await mcp.callTool({
name: "ionos_hosting_services-create-dns-records",
arguments: {
zoneId: "Zone ID",
records: "Records",
},
})import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const externalUserId = "{external_user_id}" // any stable ID for this user in your system
const [ionosHostingServicesTools, n8nIoTools] =
await Promise.all([
pd.components.list({ app: "ionos_hosting_services" }),
pd.components.list({ app: "n8n_io" }),
])
// One external user owns both connected accounts, so either app's tools
// run on their behalf with the same externalUserId.curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=ionos_hosting_services" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
curl "https://api.pipedream.com/v1/connect/{project_id}/components?app=n8n_io" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}"
# Connect both accounts to the same external_user_id, then
# configure and invoke either app's tools on that user's behalf.ARCHITECTURE
One user, two connected accounts
Your user connects each account once, under whatever ID they already have in your product. The two stay independent — either can be revoked on its own — and your code reaches both through that one user.
Your product
external_user_id
{external_user_id}Pipedream Connect
Managed identity
Auth · tools · routing
IONOS Hosting Services
Connected account
n8n.io
Connected account
TOOLS
IONOS Hosting Services tools
The IONOS Hosting Services tools this pairing puts in reach, each one running on your user's own connected account.
Actions
-
Create DNS Records
actionCreate one or more DNS records in a zone. Accepts a JSON array of record objects and returns the created records (each with a newid). Thenamefield in each record must be the fully-qualified domain name (FQDN) including the zone domain — usenewman.example.com, not justnewman. Run List DNS Zones first to get the zone ID and zone domain name, then construct the full FQDN for each record. See the documentation.Writev0.0.2 -
Delete DNS Record
actionPermanently delete a single DNS record from a zone by its record ID. This cannot be undone. Run Get DNS Zone to find the record ID. See the documentation.Writev0.0.2 -
Get DNS Record
actionGet a single DNS record from a zone by its record ID. Returns the record object, for example{"id":"rec-uuid","name":"www.example.com","type":"A","content":"5.6.7.8","ttl":3600}(full fields includerootName,prio,disabled,changeDate). Run List DNS Zones to find the zone ID and Get DNS Zone to find the record ID. See the documentation.Read-onlyv0.0.2 -
Get DNS Zone
actionGet a single DNS zone including itsrecordsarray. This is also the only way to list a zone's DNS records (there is no dedicated list-records endpoint) - use the optionalnameFilterandrecordTypefilters to narrow the returned records, and read each record'sidfor use in the record-level actions. Returns an object like{"id":"4ab3a7e2-1234-5678-abcd-ef0123456789","name":"example.com","type":"NATIVE","records":[{"id":"90d81ac0-3a30-44d4-95a5-12959effa6ee","name":"www.example.com","type":"A","content":"5.6.7.8","ttl":3600}]}. Run List DNS Zones first to obtain a zone ID. See the documentation.Read-onlyv0.0.2 -
List DNS Zones
actionList all DNS zones for the authenticated IONOS Hosting Services account. Returns an array of zone objects, for example[{"id":"4ab3a7e2-1234-5678-abcd-ef0123456789","name":"example.com","type":"NATIVE"}]. Use theidfield (not thenamefield) as the zone ID in other DNS actions. See the documentation.Read-onlyv0.0.2 -
Patch DNS Zone
actionPartially update a DNS zone (HTTP PATCH): for each provided record, all existing records sharing the same name and type are replaced with the provided ones. Records with other name/type combinations are left untouched. For a full zone overwrite use Update DNS Zone (Full Replace) instead. Run List DNS Zones to find the zone ID. See the documentation.Writev0.0.2 -
Update DNS Record
actionUpdate an existing DNS record (HTTP PUT on a single record). Onlycontent,ttl,prio, anddisabledcan be changed - the record'snameandtypeare immutable via this endpoint (delete and recreate to change them). Run Get DNS Zone to find the record ID. See the documentation.Writev0.0.2 -
Update DNS Zone (Full Replace)
actionReplace ALL records in a DNS zone with the provided record set (HTTP PUT / full zone overwrite). Any existing record not present in the payload is permanently removed. For a partial update that only replaces records sharing the same name and type, use Patch DNS Zone instead. Run List DNS Zones to find the zone ID and Get DNS Zone to inspect current records first. See the documentation.Writev0.0.2
Triggers
No IONOS Hosting Services triggers are available yet.
TOOLS
n8n.io tools
The n8n.io tools this pairing puts in reach, each one running on your user's own connected account.
Actions
No n8n.io actions are available yet.
Triggers
No n8n.io triggers are available yet.
MULTI-APP
Works with more apps
The combinations customers connect alongside these two — nothing here is limited to a pair.
REFERENCE
Toolkit details
- x-pd-app-slug
- ionos_hosting_services,n8n_io
- Primary app
- IONOS Hosting Services (ionos_hosting_services)
- Second app
- n8n.io (n8n_io)
- Authentication
- API key + API key
- Available actions
- 8
- Available triggers
- 0