MCP Servers

Discover Awesome MCP Servers

Extend your agent with 20,436 capabilities via MCP servers.

All20,436

MCP Tools

MCP (Model Context Protocol) サーバーとやり取りするためのコマンドラインインターフェース。標準入出力 (stdio) と HTTP トランスポートの両方を使用します。

Mattermost MCP Server

Claudeやその他のMCPクライアントがMattermostワークスペースと連携できるようにするMCPサーバー。チャンネル管理、メッセージング機能、トピック監視機能を提供します。

Edgeone Pages Mcp Server

EdgeOne PagesにHTMLコンテンツを迅速にデプロイし、デプロイされたコンテンツに対して自動的に公開URLを生成するサービス。

MCP Server DevOps Bridge 🚀

Azure Log Analytics MCP Server

自然言語を使用して Azure Log Analytics をクエリするための MCP サーバー

Agentis MCP

MCPサーバーをツールとして使用するAIエージェントを作成するためのPythonフレームワーク。あらゆるMCPサーバーおよびモデルプロバイダーと互換性があります。

AlphaVantage MCP Server

AlphaVantageの金融データAPIと連携し、株式市場データ、テクニカル指標、および基礎的な財務情報へのアクセスを提供するMCPサーバー。

mcp-server-iris: An InterSystems IRIS MCP server

Okay, I understand. Here's how you can execute SQL queries and perform monitoring/manipulations with Interoperability in InterSystems IRIS, along with examples and explanations: **1. Executing SQL Queries** InterSystems IRIS provides several ways to execute SQL queries: * **SQL Shell (Terminal):** The most direct way. * **Management Portal:** A web-based interface. * **Embedded SQL (ObjectScript):** Within your ObjectScript code. * **JDBC/ODBC:** From external applications. **a) SQL Shell (Terminal)** 1. **Access the Terminal:** Open the InterSystems IRIS terminal. The exact method depends on your installation (e.g., using `iris session` on Linux, or the InterSystems IRIS shortcut on Windows). 2. **Switch to the Namespace:** Use the `ZN` command to switch to the namespace where your data resides. For example: ``` ZN DEMOSPACE ``` 3. **Execute SQL:** Use the `DO $SYSTEM.SQL.Shell()` command to enter the SQL shell. Then, type your SQL queries. ``` DO $SYSTEM.SQL.Shell() SQL> SELECT Name, Age FROM Sample.Person WHERE Age > 30; ``` To exit the SQL shell, type `QUIT`. **b) Management Portal** 1. **Access the Management Portal:** Open your web browser and navigate to the Management Portal (usually `http://localhost:52773/csp/sys/UtilHome.csp`). Replace `52773` with your instance's port if it's different. 2. **Log In:** Log in with a user that has appropriate permissions (e.g., `_SYSTEM` with the password you set during installation). 3. **Navigate to SQL Shell:** Go to **System Explorer > SQL Shell**. 4. **Select Namespace:** Choose the correct namespace from the dropdown. 5. **Enter and Execute SQL:** Type your SQL query in the text area and click **Execute**. **c) Embedded SQL (ObjectScript)** This is the most common way to execute SQL within your applications. ```objectscript ClassMethod ExecuteSQL() As %Status { Set sqlCode = ##class(%SQL.Statement).%New() Set status = sqlCode.%Prepare("SELECT Name, Age FROM Sample.Person WHERE Age > ?") If $$$ISERR(status) { Quit status } Set rs = sqlCode.%Execute(40) // Example: Age > 40 If $$$ISERR(rs.%SQLCODE) { Quit rs.%SQLCODE } While rs.%Next() { Set name = rs.%Get("Name") Set age = rs.%Get("Age") Write "Name: ", name, ", Age: ", age, ! } Quit $$$OK } ``` **Explanation:** * `##class(%SQL.Statement).%New()`: Creates a new SQL statement object. * `%Prepare()`: Prepares the SQL statement for execution. Using prepared statements is crucial for performance and security (prevents SQL injection). The `?` is a placeholder for a parameter. * `%Execute()`: Executes the prepared statement, passing in the parameter value(s). * `rs.%Next()`: Iterates through the result set. * `rs.%Get("Name")`: Retrieves the value of the "Name" column for the current row. * `$$$ISERR()`: A macro that checks for errors. * `$$$OK`: A macro that represents a successful status. **d) JDBC/ODBC** You can connect to InterSystems IRIS from external applications using JDBC or ODBC drivers. The steps involve: 1. **Download the Drivers:** Obtain the JDBC or ODBC driver from the InterSystems website or the Management Portal. 2. **Configure the Driver:** Configure the driver in your application's environment (e.g., set up a JDBC connection pool). 3. **Connect and Execute:** Use the driver's API to connect to the IRIS instance and execute SQL queries. **2. Monitoring and Manipulations with Interoperability** Interoperability in InterSystems IRIS allows you to connect to and interact with external systems. Monitoring and manipulation often involve: * **Monitoring Production Processes:** Tracking the status of business processes, message queues, and other components. * **Error Handling and Alerting:** Detecting and responding to errors in message processing. * **Message Routing and Transformation:** Modifying and directing messages based on their content or other criteria. * **Data Enrichment:** Adding data from external sources to messages. * **Orchestration:** Coordinating multiple services to complete a business transaction. **Key Interoperability Components:** * **Productions:** The central component for defining and managing business processes. * **Business Operations:** Send messages to external systems. * **Business Processes:** Define the logic for processing messages. * **Business Services:** Receive messages from external systems. * **Adapters:** Handle the communication with specific external systems (e.g., file systems, databases, web services). * **Data Transformations:** Convert data between different formats. **a) Monitoring Productions** The Management Portal provides tools for monitoring productions: 1. **Navigate to Production Monitoring:** Go to **System Explorer > Production Monitoring**. 2. **View Production Status:** You can see the overall status of the production (running, stopped, etc.), as well as the status of individual business operations, processes, and services. 3. **Track Message Flow:** You can trace the flow of messages through the production, see which components have processed them, and view any errors that have occurred. 4. **View Message Details:** You can inspect the contents of messages to troubleshoot issues. **b) Manipulating Productions (Programmatically)** You can use ObjectScript to programmatically control and monitor productions. ```objectscript ClassMethod ControlProduction(productionName As %String, action As %String) As %Status { Set production = ##class(Ens.Production).%OpenId(productionName) If '$IsObject(production) { Quit $$$ERROR($$$GeneralError, "Production not found: " _ productionName) } If action = "Start" { Set status = production.Start() } elseif action = "Stop" { Set status = production.Stop() } elseif action = "Restart" { Set status = production.Restart() } else { Quit $$$ERROR($$$GeneralError, "Invalid action: " _ action) } Quit status } ClassMethod GetProductionStatus(productionName As %String) As %String { Set production = ##class(Ens.Production).%OpenId(productionName) If '$IsObject(production) { Quit "Production not found: " _ productionName } Quit production.Status } ``` **Explanation:** * `Ens.Production`: The class that represents a production. * `%OpenId()`: Opens an existing production by its name (ID). * `Start()`, `Stop()`, `Restart()`: Methods to control the production. * `Status`: A property that returns the current status of the production. **c) Error Handling and Alerting** Interoperability provides mechanisms for handling errors: * **Error Handling in Business Processes:** You can define error handlers within your business processes to catch and handle exceptions. * **Alerting:** You can configure alerts to be triggered when errors occur. These alerts can be sent via email, SMS, or other channels. * **Message Retries:** You can configure business operations to automatically retry sending messages that fail. * **Dead Letter Queues:** Messages that cannot be processed are often moved to a dead letter queue for later analysis. **Example: Error Handling in a Business Process** ```objectscript /// This is a simplified example. Real-world error handling is more complex. ClassMethod MyBusinessProcess(request As MyRequestClass) As MyResponseClass { Try { // ... Your main logic here ... Set response = ..CallExternalService(request) } Catch ex { // Handle the exception Write "Error: ", ex.Name, ", ", ex.Message, ! // Optionally, send an alert or log the error. Set response = ##class(MyResponseClass).%New() Set response.Status = "Error" Set response.ErrorMessage = ex.Message } Quit response } ``` **d) Message Routing and Transformation** * **Routing Rules:** Business processes can use routing rules to determine where to send messages based on their content or other criteria. * **Data Transformations:** You can use data transformations to convert messages between different formats (e.g., XML to JSON). InterSystems IRIS provides a graphical data transformation editor. **Example: Routing Based on Message Content** ```objectscript ClassMethod RouteMessage(request As MyRequestClass) As %String { If request.MessageType = "Order" { Quit "OrderProcess" // Route to the OrderProcess business process } elseif request.MessageType = "Invoice" { Quit "InvoiceProcess" // Route to the InvoiceProcess business process } else { Quit "DefaultProcess" // Route to a default process } } ``` **e) Data Enrichment** You can use business operations to retrieve data from external sources and add it to messages. ```objectscript ClassMethod EnrichMessage(request As MyRequestClass) As MyRequestClass { // Example: Retrieve customer data from a database Set customerId = request.CustomerID Set customer = ##class(MyCustomerClass).Get(customerId) If $IsObject(customer) { Set request.CustomerName = customer.Name Set request.CustomerAddress = customer.Address } Quit request } ``` **Important Considerations:** * **Security:** Implement proper security measures to protect your data and systems. Use secure protocols (e.g., HTTPS), authenticate users, and authorize access to resources. * **Performance:** Optimize your SQL queries and interoperability configurations for performance. Use indexes, prepared statements, and efficient data transformations. * **Error Handling:** Implement robust error handling to prevent failures and ensure data integrity. * **Monitoring:** Monitor your systems regularly to detect and resolve issues promptly. * **Logging:** Log important events and errors for auditing and troubleshooting. * **Transactions:** Use transactions to ensure data consistency when performing multiple operations. * **Namespaces:** Use namespaces to organize your code and data. * **Documentation:** Document your code and configurations thoroughly. **Example Scenario: Order Processing** 1. **Business Service:** Receives an order message (e.g., in XML format) from a web service. 2. **Data Transformation:** Transforms the XML message into a canonical format. 3. **Business Process:** * Validates the order data. * Enriches the message with customer data from a database. * Routes the message to an inventory system. * Routes the message to a payment processing system. 4. **Business Operations:** Send messages to the inventory and payment processing systems. 5. **Error Handling:** If any errors occur, the business process logs the error and sends an alert to an administrator. **How to Translate to Japanese:** To translate the above information into Japanese, you would need to translate each section and code example. Here's a general approach: 1. **Translate Headings and Explanations:** Use a translation tool (like Google Translate, DeepL, or a professional translator) to translate the headings and explanations. Review the translations carefully to ensure accuracy and clarity. 2. **Translate Code Comments:** Translate the comments within the code examples to explain what the code does. 3. **Consider Terminology:** Use consistent terminology throughout the translation. For example, decide on the best Japanese translation for "Business Process," "Business Operation," "Adapter," etc., and use those terms consistently. 4. **Test the Code:** If possible, test the translated code examples to ensure that they work correctly in a Japanese environment. Pay attention to character encoding and other locale-specific issues. **Example Translation (Partial):** **English:** **1. Executing SQL Queries** InterSystems IRIS provides several ways to execute SQL queries: * **SQL Shell (Terminal):** The most direct way. **Japanese:** **1. SQLクエリの実行** InterSystems IRISでは、SQLクエリを実行するためのいくつかの方法が提供されています。 * **SQLシェル（ターミナル）：** 最も直接的な方法です。 (SQL Sheru (Tāminaru): Mottomo chokusetsuteki na hōhō desu.) **Important Note:** While I can provide a basic translation, it's highly recommended to have a native Japanese speaker review the translation for accuracy and naturalness, especially for technical documentation. This comprehensive guide should help you get started with executing SQL queries and working with Interoperability in InterSystems IRIS. Remember to consult the official InterSystems IRIS documentation for more detailed information and specific instructions. Good luck!