MCP Integrations

Connect external tools and services via Model Context Protocol

Admin
BAM MCP Server Configuration
MCP Servers: Extend BAM capabilities with external integrations

What is MCP?

Model Context Protocol (MCP) is a standard for connecting AI assistants to external tools and data sources. BAM uses MCP to extend its capabilities beyond the core Boom PMS functionality.

With MCP integrations, BAM can:

  • Access external databases and APIs
  • Query third-party services
  • Execute specialized tools
  • Connect to custom business systems

Available MCP Servers

Boom PMS Server

Built-in MCP server providing access to your Boom PMS data:

  • Reservations and calendar data
  • Property information
  • Guest records
  • Financial transactions
  • Task management

Database Server

Direct PostgreSQL database access for advanced queries and analysis.

Web Fetch Server

Retrieve and analyze content from web pages and APIs.

Custom Servers

Connect your own MCP-compatible servers for specialized functionality.

Configuring MCP Servers

1

Open BAM Configuration

Click the gear icon in BAM Chat, then select the MCP tab.

2

View Connected Servers

See a list of currently connected MCP servers and their status.

3

Add New Server

Click "Add Server" to connect a new MCP server. Enter the server URL and any required authentication.

4

Test Connection

Verify the connection is working by clicking "Test".

5

Configure Permissions

Set what data and tools the server can access.

Using MCP Tools

Once connected, MCP server tools are available to BAM automatically. You can reference them in your requests:

Example Queries

  • "Query the database for all reservations over $500"
  • "Fetch the current weather for my property locations"
  • "Search the knowledge base for cleaning procedures"

Tool Discovery

Ask BAM "What tools are available?" to see a list of connected MCP tools and their capabilities.

Security Considerations

  • Authentication - All MCP connections use secure authentication
  • Permissions - Granular control over what each server can access
  • Audit Logging - All MCP tool usage is logged
  • Data Isolation - MCP servers only access your organization's data

Troubleshooting

Connection Failed

Verify the server URL is correct and the server is running. Check network connectivity and firewall rules.

Authentication Error

Ensure API keys or credentials are correctly configured. Some servers require periodic token refresh.

Tool Not Available

Check that the server is connected and the specific tool is enabled in permissions settings.

Slow Responses

MCP calls add latency. Consider if the external data is necessary for your query, or use cached data when available.

Pro Tips

Start with Built-in Servers
The Boom PMS MCP server is pre-configured and provides most common functionality. Explore its capabilities before adding external servers.
Review Permissions
Only grant MCP servers the minimum permissions they need. Regularly audit connected servers and revoke access for unused integrations.