Parma
Parma CRM is a relationship management app designed to help you accelerate growth by deepening and nurturing your business relationships.
Verdict
Common use cases
- Pull city datasets for policy briefs
- Audit open data catalog completeness
- Cross-reference municipal records in research
- Verify dataset metadata before analysis
- Track new datasets added to portal
Integration
- Vendor
- Parma
- Category
- crm
- Auth
- OAUTH2
- Tools
- 3
- Composio slug
parma
Tools
- Get data.json metadata
Tool to retrieve dcat-us 1.1 compliant metadata of all datasets. use when you need the complete catalog json (data.json) from parma’s open data portal.
- Get User Profile
Tool to retrieve the authenticated user's profile. use after obtaining a valid auth token to fetch current user account details.
- List Parma CKAN datasets
Tool to retrieve all dataset identifiers from the parma ckan instance. use when you need to list every available dataset id.
Setup
Setup guide
- 11. In Switchy, navigate to Settings > Integrations and click Add MCP. 2. Select Parma from the CRM category and click Connect. 3. You'll be redirected to Parma's OAuth consent screen — log in with your Parma account credentials. 4. Grant the requested scopes (typically read access to public datasets and user profile). 5. After authorization, Switchy redirects you back and confirms the connection. 6. Open any Space and type '@Parma list all dataset IDs' to test — the MCP should return a list of identifiers from the Parma CKAN instance. 7. If you see dataset IDs in the response, the connection is live and ready for queries.
What teammates see: by default, memories from Parma are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List All Datasets
@Parma list all dataset IDs available in the Parma CKAN instance so I can see what's published.Open in a Space →
Fetch Catalog Metadata
@Parma retrieve the data.json metadata for all datasets in the catalog. I need the full DCAT-US compliant file.Open in a Space →
Check User Profile
@Parma get my user profile to confirm which account is connected and what access I have.Open in a Space →
Find Datasets by Theme
@Parma list all dataset IDs, then filter for any related to transportation or infrastructure.Open in a Space →
Compare Catalog Versions
@Parma retrieve the data.json metadata and compare it to the version from last month to find what changed.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Parma list all available datasets in the open data portal and highlight any related to public transportation or mobility
Retrieved 47 datasets from Parma's CKAN instance. Transportation-related datasets include: 'bus-routes-realtime' (last updated 2024-01-15), 'parking-availability-zones' (updated daily), 'bike-sharing-stations' (live feed), and 'traffic-flow-sensors' (hourly aggregates). Each dataset includes metadata describing update frequency, format (CSV/JSON/GeoJSON), and API endpoint. The full catalog shows datasets spanning urban planning, environmental monitoring, and municipal services.
This example demonstrates the MCP's primary read capability — cataloging Parma's open data holdings. Useful for discovery before deeper analysis. Note that dataset availability and freshness depend on the municipality's publishing schedule; the MCP returns what's currently indexed, not a guaranteed real-time snapshot.
@Parma fetch the complete DCAT-US metadata for the data portal and extract all datasets tagged with 'environment' or 'sustainability'
Pulled DCAT-US 1.1 compliant data.json containing 52 dataset entries. Filtering by theme keywords 'environment' and 'sustainability' yields 9 datasets: air quality monitoring stations (PM2.5/PM10 hourly), waste collection schedules by district, green space inventory with GIS coordinates, energy consumption for municipal buildings, water quality testing results, and four climate action plan progress trackers. Each entry includes publisher info, license (mostly CC-BY-4.0), and contact email for data stewards.
This showcases the MCP's ability to retrieve structured metadata conforming to federal open data standards. Ideal for compliance checks or cross-portal integration. The metadata schema is fixed by DCAT-US spec, so parsing is predictable. However, tag consistency depends on how Parma's data team categorizes datasets — some relevant entries may use different keywords.
@Parma check my user profile permissions and confirm I have access to submit feedback on dataset quality issues
Retrieved profile for authenticated user (OAuth token valid). Account type: 'registered_user' with read access to all public datasets. Permissions include: dataset search, metadata download, API key generation. Feedback submission requires 'contributor' role, which your account does not currently hold. To request contributor access, contact the data portal admin at opendata@comune.parma.it with your use case. Profile also shows 3 saved dataset bookmarks and API usage stats (142 requests this month, well under the 10k/month limit).
This example highlights the user-context tool — useful for understanding what actions are available before attempting writes. Parma's MCP is read-heavy by design (it's an open data portal), so most users won't have write permissions. The profile check prevents failed requests and clarifies the path to elevated access if needed.
Use-case deep-dives
When Parma's open data feeds your funding pipeline
A three-person nonprofit in Parma needs to track city spending patterns to time grant applications. The Parma MCP pulls DCAT-compliant metadata from the city's open data portal, giving you a structured catalog of every published dataset without scraping HTML tables. Your team can ask Switchy to surface budget line items, contract awards, or demographic shifts that signal new funding opportunities. The OAuth2 flow means each team member authenticates once, then the workspace shares access. This works when the city publishes datasets you actually need—if Parma's portal is sparse or outdated, you're better off with manual FOIA requests. If your grant cycle depends on timely municipal data, connect this MCP and let Switchy watch the catalog for you.
Skip the scraper: pull Parma datasets into your prototype
A solo developer building a transit-accessibility app needs real-time access to Parma's CKAN datasets without writing a custom scraper. The Parma MCP's three tools let you list every dataset ID, retrieve the full data.json catalog, and confirm your OAuth token is valid—all through Switchy's shared workspace. You can prototype queries in chat, export the dataset IDs you need, then hand off the integration to a contractor without re-explaining the API. This is faster than parsing the CKAN web UI or reverse-engineering their search endpoint. The trade-off: if you need more than metadata (actual CSV downloads, spatial queries), you'll still hit CKAN's REST API directly. For early-stage civic apps that just need to know what data exists, this MCP gets you from idea to working demo in one session.
When your audit team needs a single source of truth
A five-person compliance consultancy auditing Parma city contracts needs to verify that published datasets match procurement records. The Parma MCP gives your team a shared OAuth2 connection to the open data portal, so anyone can pull the latest data.json without asking IT for API keys. You ask Switchy to compare dataset publication dates against contract milestones, flag missing datasets, or export the catalog for your Excel-based audit trail. This works when the city's CKAN instance is the authoritative source—if datasets lag weeks behind internal systems, you're chasing ghosts. The three-tool scope is narrow, so expect to supplement with manual downloads for the actual data files. If your audit hinges on metadata completeness and your team hates credential sprawl, this MCP keeps everyone on the same page.
Frequently asked
What does the Parma MCP do in Switchy?
The Parma MCP connects your team to Parma's open data portal, letting AI agents retrieve dataset catalogs, list available datasets, and pull user profile details. It's built for teams working with public sector data who want to query Parma's CKAN instance without writing API calls manually. The three tools cover metadata retrieval and account verification.
Does the Parma MCP require OAuth2 approval from an admin?
Yes, it uses OAuth2, so you'll need to authorize Switchy through Parma's authentication flow. The MCP requests scopes to read dataset metadata and your user profile — no write permissions. If your Parma account is part of an organization, check whether your IT team restricts third-party OAuth apps before connecting.
Can the Parma MCP update or publish datasets?
No. The three available tools are read-only: they fetch the data.json catalog, list dataset IDs, and retrieve your user profile. If you need to upload datasets or modify metadata, use Parma's web interface or API directly. This MCP is for discovery and retrieval, not data management.
Why use the Parma MCP instead of calling the CKAN API directly?
The MCP wraps Parma's CKAN endpoints so your AI agents can query datasets in natural language without you writing pagination logic or parsing JSON responses. If your team already has CKAN scripts, you don't need this. If you want agents to answer questions like 'show me all environmental datasets', the MCP handles the API calls for you.
Who on the team should connect the Parma MCP?
Anyone with a valid Parma account can connect it. Since the tools are read-only, you don't need admin privileges on the Parma side. One team member should connect it, then share the workspace so everyone's agents can query the same datasets. The connection doesn't count against Switchy seat limits.